Handling uplink transmissions for multi-trp operation

ABSTRACT

Systems, devices, and techniques for wireless communications are described. A described technique includes receiving, by a user equipment (UE) from one or more Transmission and Reception Points (TRPs), a physical downlink shared channel (PDSCH) transmission; determining, by the UE for a physical uplink control channel (PUCCH) carrying hybrid automatic repeat request-acknowledgement (HARQ-ACK), a TRP index in accordance with a control resource set (CORESET) scheduling the PDSCH transmission; and transmitting, by the UE via the PUCCH, HARQ-ACK information based on the receiving of the PDSCH transmission in accordance with the TRP index.

CROSS-REFERENCE TO RELATED APPLICATION

This disclosure claims the benefit of the priority of U.S. Provisional Patent Application No. 62/825,688, entitled “ON HANDLING OVERLAPPING BETWEEN PUCCH AND PUSCH FOR MULTI-TRP OPERATION” and filed on Mar. 28, 2019. The above-identified application is incorporated herein by reference in its entirety.

TECHNICAL FIELD

This disclosure relates generally to wireless communication systems.

BACKGROUND

Base stations, such as a node of radio access network (R N), can wirelessly communicate with wireless devices such as user equipment (UE). A downlink (DL) transmission refers to a communication from the base station to the wireless device. An uplink (UL) transmission refers to a communication from the wireless device to another device such as the base station. Base stations can transmit control signaling in order to control wireless devices that operate within their network.

SUMMARY

Systems, devices, and techniques for wireless communications are described. A described technique includes receiving, by a LIE from one or more Transmission and Reception Points (TRPs), a physical downlink shared channel (PDSCH) transmission; determining, by the UE for a physical uplink control channel (PUCCH) carrying hybrid automatic repeat request-acknowledgement (HARQ-ACK), a TRP index in accordance with a control resource set (CORESET) scheduling the PDSCH transmission; and transmitting, by the UE via the PUCCH, HARQ-ACK information based on the receiving of the PDSCH transmission in accordance with the TRP index. Other implementations include corresponding systems, apparatus, and computer programs to perform the actions of methods defined by instructions encoded on computer readable storage.

These and other implementations can include one or more of the following features. In some implementations, the CORESET can include a first CORESET and a second CORESET. The first CORESET can be associated with the first index value. The second CORESET can be associated with a second index value. The TRP index can include the first index value. Determining the TRP index can include determining the first index value associated with the first CORESET and determining a second index value associated with the second CORESET Transmitting the HARQ-ACK information can be responsive to the first index value and the second index value. Transmitting the HARQ-ACK information can include transmitting first HARQ-ACK information associated with the first CORESET; and transmitting second HARQ-ACK information associated with the second CORESET. Determining the first index value can include using a default value for the first index value based on the first index value not being provided by a network. Determining the first index can include using a CORESET index parameter configured by a radio resource control (RRC) layer. Transmitting the HARQ-ACK information can include using the first index value and the second index value for HARQ-ACK codebook construction.

In some implementations, the TRP index is indicated by a ConfiguredGrantConfig information element provided by a RRC layer. The UE can be configured to transmit, on a physical uplink control channel (PUCCH), semi-persistent channel state information based on a TRP index configured by a RRC layer. The UE can be configured to transmit, on a physical uplink shared channel (PUSCH), semi-persistent channel state information based on a TRP index configured by a RRC layer. In some implementations, receiving the PDSCH transmission can include receiving transmissions from multiple TRPs.

The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an example of a wireless communication system.

FIG. 2 illustrates an example architecture of a system including a core network.

FIG. 3 illustrates another example architecture of a system including a core network.

FIG. 4 illustrates an example of infrastructure equipment.

FIG. 5 illustrates an example of a platform or device.

FIG. 6 illustrates example components of baseband circuitry and radio front end circuitry.

FIG. 7 illustrates example components of cellular communication circuitry.

FIG. 8 illustrates example protocol functions that can be implemented in wireless communication systems.

FIG. 9 illustrates an example of a computer system.

FIG. 10 illustrates a flowchart of an example uplink communication process.

FIG. 11 illustrates a diagram of an example wireless communication system that includes multiple TRP nodes.

FIG. 12 illustrates an example of a transmission timing based dropping rule.

FIG. 13 illustrates an example of a dropping rule based on a TRP index.

FIG. 14 illustrates an example of a multiplexing rule for when PUCCH overlaps with two PUSCHs within a PUCCH group.

FIG. 15 illustrates another example of a multiplexing rule for when PUCCH overlaps with two PUSCHs within a PUCCH group.

FIG. 16 illustrates another example of a multiplexing rule for when PUCCH overlaps with two PUSCHs within a PUCCH group.

FIG. 17 illustrates an example of a multiplexing rule when two PUCCHs overlap with two PUSCHs.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 illustrates an example of a wireless communication system 100. For purposes of convenience and without limitation, the example system 100 is described in the context of the LTE and 5G NR communication standards as defined by the Third Generation Partnership Project (3GPP) technical specifications. However, other types of communication standards are possible.

The system 100 includes UE 101 a and UE 101 b (collectively referred to as the “UEs 101”). In this example, the UEs 101 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks). in other examples, any of the UEs 101 may include other mobile or non-mobile computing devices, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, machine-type communications (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, or combinations of them, among others.

In some implementations, any of the UEs 101 may be IoT UEs, which can include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as M2M or MTC for exchanging data with an MTC server or device using, for example, a public land mobile network (PLMN), proximity services (ProSe), device-to-device (D2D) communication, sensor networks, IoT networks, or combinations of them, among others. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages or status updates) to facilitate the connections of the IoT network.

The UEs 101 are configured to connect (e.g., communicatively couple) with RAN 110. The RAN 110 can include one or more RAN nodes 111 a and 111 b (collectively referred to as “RAN nodes 111” or “RAN node 111”). In some implementations, the RAN 110 may be a next generation RAN (NG RAN), an evolved UMTS terrestrial radio access network (E-UTRAN), or a legacy RAN, such as a UMTS terrestrial radio access network (UTRAN) or a GSM EDGE radio access network (GERAN). As used herein, the term “NG RAN” may refer to a RAN 110 that operates in a 5G NR system 100, and the term “E-UTRAN” may refer to a RAN 110 that operates in an LTE or 4G system 100.

To connect to the RAN 110, the UEs 101 utilize connections (or channels) 103 and 104, respectively, each of which may include a physical communications interface or layer, as described below. In this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a global system for mobile communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a PTT over cellular (POC) protocol, a universal mobile telecommunications system (UNITS) protocol, a 3GPP LTE protocol, a 5G NR protocol, or combinations of them, among other communication protocols.

The RAN 110 can include one or more RAN nodes 111 a and 111 b (collectively referred to as “RAN nodes 111” or “RAN node 111”) that enable the connections 103 and 104. As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data or voice connectivity, or both, between a network and one or more users. These access nodes can be referred to as base stations (BS), gNodeBs, gNBs, eNodeBs, eNBs, NodeBs, RAN nodes, road side units (RSUs), and the like, and can include ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell), among others. As used herein, the term “NG RAN node” may refer to a RAN node 111 that operates in a 5G NR system 100 (for example, a gNB), and the term “E-UTRAN node” may refer to a RAN node 111 that operates in an LTE or 4G system 100 (e.g., an eNB). In some implementations, the RAN nodes 111 may be implemented as one or more of a dedicated physical device such as a macrocell base station, or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

The RAN nodes 111 and the UEs 101 can be configured for multiple-input and multiple-output (MIMO) communications, including single or multi-beam communications. For example, a UE 101 can receive transmissions from one RAN node 111 at a time or from multiple RAN nodes 111 at the same time. The RAN nodes 111 and the UEs 101 can use beamforming for the UL, DL, or both. For example, one or more RAN nodes 111 can transmit (TX) a beam towards a UE 101, and the UE 101 can receive data via one or more TX beams at the same time, In some implementations, each of the RAN nodes 111 can he configured as a Transmission and Reception Point (TRP). The RAN 110 can provide a high-layer signaling protocol for configuring beamforming such as by providing transmission configuration indication (TCI) state configuration information.

Any of the RAN nodes 111 can terminate the air interface protocol and can be the first point of contact for the UEs 101. In some implementations, any of the RAN nodes 111 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

In some implementations, the UEs 101 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 111 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques for uplink communications), although the scope of the techniques described here not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

The RAN nodes 111 can transmit to the UEs 101 over various channels. Various examples of downlink communication channels include Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), and Physical Downlink Shared Channel (PDSCH). Other types of downlink channels are possible. The UEs 101 can transmit to the RAN nodes 111 over various channels. Various examples of uplink communication channels include Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random Access Channel (PRACH). Other types of uplink channels are possible.

In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 111 to the UEs 101, while uplink transmissions can utilize similar techniques. The grid can be a frequency grid or a time-frequency grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks. In some implementations, a physical resource block (PRB) can include a number of resource blocks. A PCB can be used as a unit in a frequency-domain resource allocation for channels such as PDSCH.

The PDSCH carries user data and higher-layer signaling to the UEs 101. The PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 101 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Downlink scheduling (e.g., assigning control and shared channel resource blocks to the UE 101 b within a cell) may be performed at any of the RAN nodes 111 based on channel quality information fed back from any of the UEs 101. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 101.

The PDCCH can convey scheduling information of different types. Scheduling information can include downlink resource scheduling, uplink power control instructions, uplink resource grants, and indications for paging or system information. The RAN nodes 111 can transmit one or more downlink control information (DCI) messages on the PDCCH to provide scheduling information, such as allocations of one or more PRBs, for downlink channels, uplink channels, or both.

In some implementations, the PDCCH uses control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. In some implementations, each PDCCH may be transmitted using one or more of these CCEs, in which each CCE may correspond to nine sets of four physical resource elements collectively referred to as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of DCI and the channel condition. In some implementations, there can be four or more different PDCCH formats defined with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

In some implementations, the PDCCH is transmitted via on one or more CORESETs. A CORESET can correspond to a set of time-frequency resources. A CORESET can provide one or more locations where a UE 101 can receive PDCCH. In some implementations, CORESETs are semi-statically configured by the network.

The RAN nodes 111 are configured to communicate with one another using an interface 112. In examples, such as where the system 100 is an LTE system (e.g., when the core network 120 is an evolved packet core (EPC) network as shown in FIG. 2), the interface 112 may be an X2 interface 112. The X2 interface may be defined between two or more RAN nodes 111 (e.g., two or more eNBs and the like) that connect to the EPC 120, or between two eNBs connecting to EPC 120, or both. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a master eNB to a secondary eNB; information about successful in sequence delivery of PDCP protocol data units (PDUs) to a UE 101 from a secondary eNB for user data; information of PDCP PDUs that were not delivered to a LE 101; information about a current minimum desired buffer size at the secondary eNB for transmitting to the UE user data, among other information. The X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs or user plane transport control; load management functionality; inter-cell interference coordination functionality, among other functionality.

In some implementations, such as where the system 100 is a 5G NR system (e.g., when the core network 120 is a 5G core network as shown in FIG. 3), the interface 112 may be an Xn interface 112. The Xn interface may be defined between two or more RAN nodes 111 (e.g., two or more gNBs and the like) that connect to the 5G core network 120, between a RAN node 111 (e.g., a gNB) connecting to the 5G core network 120 and an eNB, or between two eNBs connecting to the 5G core network 120, or combinations of them. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 101 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes 111, among other functionality. The mobility support may include context transfer from an old (source) serving RAN node 111 to new (target) serving RAN node 111, and control of user plane tunnels between old (source) serving RAN node 111 to new (target) serving RAN node 111. A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GPRS tunneling protocol for user plane (GTP-U) layer on top of a user datagram protocol (UDP) or IP layer(s), or both, to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP or XnAP)) and a transport network layer that is built on a stream control transmission protocol (SCTP). The SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack or the Xn-C protocol stack, or both, may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

The RAN 110 is shown to be communicatively coupled to a core network 120 (referred to as a “CN 120”). The CN 120 includes one or more network elements 122, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 101) who are connected to the CN 120 using the RAN 110. The components of the CN 120 may be implemented in one physical node or separate physical nodes and may include components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network functions virtualization (NFV) may be used to virtualize some or all of the network node functions described here using executable instructions stored in one or more computer-readable storage mediums, as described in further detail below. A logical instantiation of the CN 120 may be referred to as a network slice, and a logical instantiation of a portion of the CN 120 may be referred to as a network sub-slice. NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more network components or functions, or both.

An application server 130 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS packet services (PS) domain, LTE PS data services, among others). The application server 130 can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, among others) for the UEs 101 using the CN 120. The application server 130 can use an IP communications interface 125 to communicate with one or more network elements 122.

In some implementations, the CN 120 may be a 5G core network (referred to as “5GC 120” or “5G core network 120”), and the RAN 110 may be connected with the CN 120 using a next generation interface 113. In some implementations, the next generation interface 113 may be split into two parts, an next generation user plane (NG-U) interface 114, which carries traffic data between the RAN nodes 111 and a user plane function (UPF), and the S1 control plane (NG-C) interface 115, which is a signaling interface between the RAN nodes 111 and access and mobility management functions (AMFs). Examples where the CN 120 is a 5G core network are discussed in more detail with regard to FIG. 3.

In some implementations, the CN 120 may be an EPC (referred to as “EPC 120” or the like), and the RAN 110 may be connected with the CN 120 using an S1 interface 113. In some implementations, the S1 interface 113 may be split into two parts, an S1 user plane (S1-U) interface 114, which carries traffic data between the RAN nodes 111 and the serving gateway (S-GW), and the S1-MME interface 115, which is a signaling interface between the RAN nodes 111 and mobility management entities (MMEs).

In some implementations, the UEs 101 may directly exchange communication data using an interface 105, such as a ProSe interface. The interface 105 may alternatively be referred to as a sidelink interface 105 and may include one or more logical channels, such as a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink downlink channel (PSDCH), or a physical sidelink broadcast channel (PSBCH), or combinations of them, among others.

The UE 101 b is shown to be configured to access an access point (AP) 106 (also referred to as “WLAN node 106,” “WLAN 106,” “WLAN Termination 106,” “WT 106” or the like) using a connection 107. The connection 107 can include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, in which the AP 106 would include a wireless fidelity (Wi-Fi) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system, as described in further detail below. In various examples, the UE 101 b, RAN 110, and AP 106 may be configured to use LTE-WLAN aggregation (LWA) operation or LTW/WLAN radio level integration with IPsec tunnel (LWIP) operation. The LWA operation may involve the UE 101 b in RRC_CONNECTED being configured by a RAN node 111 a, 111 b to utilize radio resources of LTE and WLAN. LWIP operation may involve the UE 101 b using WLAN radio resources (e.g., connection 107) using IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection 107. IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

In some implementations, some or all of the RAN nodes 111 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a cloud RAN (CRAN) or a virtual baseband unit pool (vBBUP). The CRAN or vBBUP may implement a RAN function split, such as a packet data convergence protocol (PDCP) split in which radio resource control (RRC) and PDCP layers are operated by the CRAN/vBBUP and other layer two (e.g., data link layer) protocol entities are operated by individual RAN nodes 111; a medium access control (MAC)/physical layer (PHY) split in which RRC, PDCP, MAC, and radio link control (RLC) layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes 111; or a “lower PHY” split in which RRC, PDCP, RLC, and MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes 111. This virtualized framework allows the freed-up processor cores of the RAN nodes 111 to perform, for example, other virtualized applications. In some implementations, an individual RAN node 111 may represent individual gNB distributed units (DUs) that are connected to a gNB central unit (CU) using individual F1 interfaces (not shown in FIG. 1). In some implementations, the gNB-DUs may include one or more remote radio heads or RFEMs (see, e.g., FIG. 4), and the gNB-CU may be operated by a server that is located in the RAN 110 (not shown) or by a server pool in a similar manner as the CRAN/vBBUP. Additionally or alternatively, one or more of the RAN nodes 111 may be next generation eNBs (ng-eNBs), including RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UEs 101, and are connected to a 5G core network (e.g., core network 120) using a next generation interface.

In vehicle-to-everything (V2X) scenarios, one or more of the RAN nodes 111 may be or act as RSUs. The term “Road Side Unit” or “RSU” refers to any transportation infrastructure entity used for V2X communications. A RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where a RSU implemented in or by a UE may be referred to as a “UE-type RSU,” a RSU implemented in or by an eNB may be referred to as an “eNB-type RSU,” a RSU implemented in or by a gNB may be referred to as a “gNB-type RSU,” and the like. In some implementations, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs 101 (vUEs 101). The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications or other software to sense and control ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communications services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) or provide connectivity to one or more cellular networks to provide uplink and downlink communications, or both. The computing device(s) and some or all of the radiofrequency circuitry of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network, or both.

FIG. 2 illustrates an example architecture of a system 200 including a first CN 220. In this example, the system 200 may implement the LTE standard such that the CN 220 is an EPC 220 that corresponds with CN 120 of FIG. 1. Additionally, the UE 201 may be the same or similar as the UEs 101 of FIG. 1, and the E-UTRAN 210 may be a RAN that is the same or similar to the RAN 110 of FIG. 1, and which may include RAN nodes 111 discussed previously. The CN 220 may comprise MMEs 221, an S-GW 222, a PDN gateway (P-GW) 223, a high-speed packet access (HSS) function 224, and a serving CPRS support node (SGSN) 225.

The MMEs 221 may be similar in function to the control plane of legacy SGSN, and may implement mobility management (MM) functions to keep track of the current location of a UE 201. The MMEs 221 may perform various mobility management procedures to manage mobility aspects in access such as gateway selection and tracking area list management. Mobility management (also referred to as “EPS MM” or “EMM” in E-UTRAN systems) may refer to all applicable procedures, methods, data storage, and other aspects that are used to maintain knowledge about a present location of the UE 201, provide user identity confidentiality, or perform other like services to users/subscribers, or combinations of them, among others. Each UE 201 and the MME 221 may include an EMM sublayer, and an mobility management context may be established in the UE 201 and the MME 221 when an attach procedure is successfully completed. The mobility management context may be a data structure or database object that stores mobility management-related information of the UE 201. The MMEs 221 may be coupled with the HSS 224 using a S6 a reference point, coupled with the SGSN 225 using a S3 reference point, and coupled with the S-GW 222 using a S11 reference point.

The SGSN 225 may be a node that serves the UE 201 by tracking the location of an individual UE 201 and performing security functions. In addition, the SGSN 225 may perform Inter-EPC node signaling for mobility between 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by the MMEs 221; handling of UE 201 time zone functions as specified by the MMEs 221; and MME selection for handovers to E-UTRAN 3GPP access network, among other functions. The S3 reference point between the MMEs 221 and the SGSN 225 may enable user and bearer information exchange for inter-3GPP access network mobility in idle or active states, or both.

The HSS 224 may include a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The EPC 220 may include one or more HSSs 224 depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, or combinations of them, among other features. For example, the HSS 224 can provide support for routing, roaming, authentication, authorization, naming/addressing resolution, location dependencies, among others. A S6 a reference point between the HSS 224 and the MMEs 221 may enable transfer of subscription and authentication data for authenticating or authorizing user access to the EPC 220 between HSS 224 and the MMEs 221.

The S-GW 222 may terminate the S1 interface 113 (“S1-U” in FIG. 2) toward the RAN 210, and may route data packets between the RAN 210 and the EPC 220. In addition, the S-GW 222 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement, The S11 reference point between the S-GW 222 and the MMEs 221 may provide a control plane between the MMEs 221 and the S-GW 222. The S-GW 222 may be coupled with the P-GW 22.3 using a S5 reference point.

The P-GW 223 may terminate a SGi interface toward a PDN 230, The P-GW 223 may route data packets between the EPC 220 and external networks such as a network including the application server 130 (sometimes referred to as an “AF”) using an IP communications interface 125 (see, e.g., FIG. 1). In some implementations, the P-GW 223 may be communicatively coupled to an application server (e.g., the application server 130 of FIG. 1 or PDN 230 in FIG. 2) using an IP communications interface 125 (see, e.g., FIG. 1). The S5 reference point between the P-GW 223 and the S-GW 222 may provide user plane tunneling and tunnel management between the P-GW 223 and the S-GW 222. The S5 reference point may also be used for S-GW 222 relocation due to UE 201 mobility and if the S-GW 222 needs to connect to a non-collocated P-GW 223 for the required PDN connectivity. The P-GW 223 may further include a node for policy enforcement and charging data collection (e.g., PCEF (not shown)). Additionally, the SGi reference point between the P-GW 223 and the packet data network (PDN) 230 may be an operator external public, a private PDN, or an intra operator packet data network, for example, for provision of IMS services. The P-GW 223 may be coupled with a policy control and charging rules function (PCRF) 226 using a Gx reference point.

PCRF 226 is the policy and charging control element of the EPC 220. In a non-roaming scenario, there may be a single PCRF 226 in the Home Public Land Mobile Network (HPLMN) associated with a UE 201's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE 201's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 226 may be communicatively coupled to the application server 230 using the P-GW 223. The application server 230 may signal the PCRF 226 to indicate a new service flow and select the appropriate quality of service (QoS) and charging parameters. The PCRF 226 may provision this rule into a PCEF (not shown) with the appropriate traffic flow template (TFT) and QoS class identifier (QCI), which commences the QoS and charging as specified by the application server 230. The Gx reference point between the PCRF 226 and the P-GW 223 may allow for the transfer of QoS policy and charging rules from the PCRF 226 to PCEF in the P-GW 223. A Rx reference point may reside between the PDN 230 (or “AF 230”) and the PCRF 226.

FIG. 3 illustrates an architecture of a system 300 including a second CN 320. The system 300 is shown to include a UE 301, which may be the same or similar to the UEs 101 and UE 201 discussed previously; a RAN 310, which may be the same or similar to the RAN 110 and RAN 210 discussed previously, and which may include RAN nodes 111 discussed previously; and a data network (DN) 303, which may be, for example, operator services, Internet access or 3rd party services; and a SGC 320. The 5GC 320 may include an authentication server function (AUSF) 322; an access and mobility management function (AMF) 321; a session management function (SW) 324; a network exposure function (NEF) 323; a policy control function (PCF) 326; a network repository function (NRF) 325; a unified data management (UDM) function 327; an AF 328; a user plane function (UPF) 302.; and a network slice selection function (NSSF) 329.

The UPF 302 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN 303, and a branching point to support multi-homed PDU session. The LW 302 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform Uplink Traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 302 may include an uplink classifier to support routing traffic flows to a data network. The DN 303 may represent various network operator services, Internet access, or third party services. DN 303 may include, or be similar to, application server 130 discussed previously. The UPF 302 may interact with the SMF 324 using a N4 reference point between the SMF 324 and the UPF 302.

The AUSF 322 stores data for authentication of UE 301 and handle authentication-related functionality. The AUSF 322 may facilitate a common authentication framework for various access types. The AUSF 322 may communicate with the AMF 321 using a N12 reference point between the AMF 321 and the AUSF 322, and may communicate with the UDM 327 using a N13 reference point between the UDM 327 and the AUSF 322. Additionally, the AUSF 322 may exhibit a Nausf service-based interface.

The AMF 321 is responsible for registration management (e.g., for registering UE 301), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF 321 may be a termination point for the N11 reference point between the AMF 321 and the SMF 324. The AMF 321 may provide transport for SM messages between the UE 301 and the SMF 324, and act as a transparent pro10 for routing SM messages. AMF 321 may also provide transport for SMS messages between UE 301 and an SMSF (not shown in FIG. 3). AMF 321 may act as security anchor function (SEAF), which may include interaction with the AUSF 322 and the LTE 301 to, for example, receive an intermediate key that was established as a result of the UE 301 authentication process. Where universal subscriber identity module (USIM) based authentication is used, the AMF 321 may retrieve the security material from the AUSF 322. AMF 321 may also include a security context management (SCM) function, which receives a key from the SEAF to derive access-network specific keys. Furthermore, AMF 321 may be a termination point of a RAN control plane interface, which may include or be a N2 reference point between the RAN 310 and the AMF 321. In some implementations, the ATF 321 may be a termination point of NAS (N1) signaling and perform NAS ciphering and integrity protection.

AMF 321 may also support NAS signaling with a UE 301 over a N3 inter-working function (IWF) interface (referred to as the “N3IWF”). The N3IWF may be used to provide access to entrusted entities. The N3IWF may be a termination point for the N2 interface between the RAN 310 and the AMF 321 for the control plane, and may be a termination point for the N3 reference point between the RAN 310 and the UPF 302 for the user plane. As such, the AMF 321 may handle N2 signaling from the SMF 324 and the AMF 321 for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPsec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2. The N3IWF may also relay uplink and downlink control-plane NAS signaling between the UE 301 and AMF 321 using a N1 reference point between the UE 301 and the AMF 321, and relay uplink and downlink user-plane packets between the UE 301 and UPF 302. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 301. The AMF 321 may exhibit a Namf service-based interface, and may be a termination point for a N14 reference point between two AMFs 321 and a N17 reference point between the AMF 321 and a 5G equipment identity registry (EIR) (not shown in FIG. 3).

The UE 301 may register with the AMF 321 in order to receive network services. Registration management (RM) is used to register or deregister the UE 301 with the network (e.g., AMF 321), and establish a UE context in the network (e.g., AMF 321). The UE 301 may operate in a RM-REGISTERED state or an RM-DEREGISTERED state. In the RM DEREGISTERED state, the UE 301 is not registered with the network, and the UE context in AMF 321 holds no valid location or routing information for the UE 301 so the UE 301 is not reachable by the AMT 321. In the RM REGISTERED state, the UE 301 is registered with the network, and the UE context in AMF 321 may hold a valid location or routing information for the UE 301 so the UE 301 is reachable by the AMF 321. In the RM-REGISTERED state, the UE 301 may perform mobility Registration Update procedures, perform periodic Registration Update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 301 is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

The AMF 321 may store one or more RM contexts for the UE 301, where each RM context is associated with a specific access to the network. The RM context may be, for example, a data structure or database object, among others, that indicates or stores a registration state per access type and the periodic update timer. The AMF 321 may also store a 5GC mobility management (MM) context that may be the same or similar to the (E)MM context discussed previously. In some implementations, the AMF 321 may store a coverage enhancement mode B Restriction parameter of the UE 301 in an associated MM context or RM context. The AMF 321 may also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and/or MM/RM context).

Connection management (CM) may be used to establish and release a signaling connection between the UE 301 and the AMF 321 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 301 and the CN 320, and includes both the signaling connection between the E and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 301 between the AN (e.g., RAN 310) and the AMF 321. In some implementations, the UE 301 may operate in one of two CM modes: CM-IDLE mode or CM-CONNECTED mode. When the UE 301 is operating in the CM-IDLE mode, the UE 301 may have no NAS signaling connection established with the AMF 321 over the N1 interface, and there may be RAN 310 signaling connection (e.g., N2 or N3 connections, or both) for the UE 301. When the UE 301 is operating in the CM-CONNECTED mode, the UE 301 may have an established NAS signaling connection with the AMF 321 over the N1 interface, and there may be a RAN 310 signaling connection (e.g., N2 and/or N3 connections) for the UE 301. Establishment of a N2 connection between the RAN 310 and the AMF 321 may cause the UE 301 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and the UE 301 may transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the RAN 310 and the AMF 321 is released.

The SMF 324 may be responsible for session management (SM), such as session establishment, modify and release, including tunnel maintain between UPF and AN node; UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at the UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent using AMF over N2 to AN; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session (or “session”) may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 301 and a data network (DN) 303 identified by a Data Network Name (DNN). PDU sessions may be established upon UE 301 request, modified upon UE 301 and 5GC 320 request, and released upon UE 301 and SGC 320 request using NAS SM signaling exchanged over the N1 reference point between the UE 301 and the SMF 324. Upon request from an application server, the 5GC 320 may trigger a specific application in the UE 301. In response to receipt of the trigger message, the UE 301 may pass the trigger message (or relevant parts/information of the trigger message) to one or more identified applications in the UE 301. The identified application(s) in the UE 301 may establish a PDU session to a specific DNN. The SMF 324 may check whether the UE 301 requests are compliant with user subscription information associated with the UE 301. In this regard, the SMF 324 may retrieve and/or request to receive update notifications on SMF 324 level subscription data from the UDM 327.

The SMF 324 may include some or all of the following roaming functionality: handling local enforcement to apply QoS service level agreements (SLAs) (e.g., in VPLMN); charging data collection and charging interface (e.g., in VPLMN); lawful intercept (e.g., in VPLMN for SM events and interface to LI system); and support for interaction with external DN for transport of signaling for PDU session authorization/authentication by external DN. A N16 reference point between two SMFs 324 may be included in the system 300, which may be between another SMF 324 in a visited network and the SMF 324 in the home network in roaming scenarios. Additionally, the SMF 324 may exhibit the Nsmf service-based interface.

The NEF 323 may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, Application Functions (e.g., AF 328), edge computing or fog computing systems, among others. In some implementations, the NEF 323 may authenticate, authorize, and/or throttle the AFs. The NEF 323 may also translate information exchanged with the AF 328 and information exchanged with internal network functions. For example, the NEF 323 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 323 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 323 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 323 to other NFs and AFs, or used for other purposes such as analytics, or both. Additionally, the NEF 323 may exhibit a Nnef service-based interface.

The NRF 325 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 325 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 325 may exhibit the Nnrf service-based interface.

The PCF 326 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behavior. The PCF 326 may also implement a front end to access subscription information relevant for policy decisions in a unified data repository (UDR) of the UDM 327. The PCF 326 may communicate with the AMF 321 using an N15 reference point between the PCF 326 and the AMF 321, which may include a PCF 326 in a visited network and the AMF 321 in case of roaming scenarios. The PCF 326 may communicate with the AF 328 using a N5 reference point between the PCF 326 and the AF 328; and with the SMF 324 using a N7 reference point between the PCF 326 and the SMF 324. The system 300 or CN 320, or both, may also include a N24 reference point between the PCF 326 (in the home network) and a PCF 326 in a visited network. Additionally, the PCF 326 may exhibit a Npcf service-based interface.

The UDM 327 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 301. For example, subscription data may be communicated between the UDM 327 and the AMF 321 using a N8 reference point between the UDM 327 and the AMF. The UDM 327 may include two parts, an application front end and a UDR (the front end and UDR are not shown in FIG. 3). The UDR may store subscription data and policy data for the UDM 327 and the PCF 326, or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 301) for the NEF 323, or both. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 327, PCF 326, and NEF 323 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM front end, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM front end accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. The UDR may interact with the SMF 324 using a N10 reference point between the UDM 327 and the SMF 324. UDM 327 may also support SMS management, in which an SMS front end implements the similar application logic as discussed previously. Additionally, the UDM 327 may exhibit the Nudm service-based interface.

The AF 328 may provide application influence on traffic routing, provide access to the network capability exposure (NCE), and interact with the policy framework for policy control. The NCE may be a mechanism that allows the 5GC 320 and AF 328 to provide information to each other using NEF 323, which may be used for edge computing implementations. In such implementations, the network operator and third party services may be hosted close to the UE 301 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF 302 close to the UE 301 and execute traffic steering from the UPF 302 to DN 303 using the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 328. In this way, the AF 328 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 328 is considered to be a trusted entity, the network operator may permit AF 328 to interact directly with relevant NFs. Additionally, the AF 328 may exhibit a Naf service-based interface.

The NSSF 329 may select a set of network slice instances serving the UE 301. The NSSF 329 may also determine allowed NSSAI and the mapping to the subscribed single network slice selection assistance information (S-NSSAI), if needed. The NSSF 329 may also determine the AMF set to be used to serve the UE 301, or a list of candidate AMF(s) 321 based on a suitable configuration and possibly by querying the NRF 325. The selection of a set of network slice instances for the UE 301 may be triggered by the AMF 321 with which the UE 301 is registered by interacting with the NSSF 329, which may lead to a change of AMF 321. The NSSF 329 may interact with the AMF 321 using an N22 reference point between AMF 321 and NSSF 329; and may communicate with another NSSF 329 in a visited network using a N31 reference point (not shown by FIG. 3). Additionally, the NSSF 329 may exhibit a Nnssf service-based interface.

As discussed previously, the CN 320 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to or from the UE 301 to or from other entities, such as an SMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 321 and UDM 327 for a notification procedure that the UE 301 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 327 when UE 301 is available for SMS).

In some implementations, there may be additional or alternative reference points or service-based interfaces, or both, between the network function services in the network functions. However, these interfaces and reference points have been omitted from FIG. 3 for clarity. in one example, the CN 320 may include a Nx interface, which is an inter-CN interface between the MME (e.g., MME 221) and the AMF 321 in order to enable interworking between CN 320 and CN 220. Other example interfaces or reference points may include a N5g-EIR service-based interface exhibited by a 5G-EIR, a N27 reference point between the NRF in the visited network and the NRF in the home network, or a N31 reference point between the NSSF in the visited network and the NSSF in the home network, among others.

In some implementations, the components of the CN 220 may be implemented in one physical node or separate physical nodes and may include components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium), in some implementations, the components of CN 320 may be implemented in a same or similar manner as discussed herein with regard to the components of CN 220. In some implementations, NFV is utilized to virtualize any or all of the above-described network node functions using executable instructions stored in one or more computer-readable storage mediums, as described in further detail below. A logical instantiation of the CN 220 may be referred to as a network slice, and individual logical instantiations of the CN 220 may provide specific network capabilities and network characteristics, A logical instantiation of a portion of the CN 220 may be referred to as a network sub-slice, which can include the P-GW 223 and the PCRF 226.

As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. A network instance may refer to information identifying a domain, which may be used for traffic detection and routing in case of different IP domains or overlapping IP addresses. A network slice instance may refer to a set of network functions (NFs) instances and the resources (e.g., compute, storage, and networking resources) required to deploy the network slice.

With respect to 5G systems (see, e.g., FIG. 3), a network slice may include a RAN part and a CN part. The support of network slicing relies on the principle that traffic for different slices is handled by different PDL sessions. The network can realize the different network slices by scheduling or by providing different L1/L2 configurations, or both. The UE 301 provides assistance information for network slice selection in an appropriate RRC message if it has been provided by NAS. While the network can support large number of slices, the UE need not support more than 8 slices simultaneously in some implementations.

A network slice may include the CN 320 control plane and user plane NFs, NG-RANs 310 in a serving PLMN, and a N3IWF functions in the serving PLMN. Individual network slices may have different S-NSSAI or different SSTs, or both. NSSAI includes one or more S-NSSAIs, and each network slice is uniquely identified by an S-NSSAI. Network slices may differ for supported features and network functions optimizations. In some implementations, multiple network slice instances may deliver the same services or features but for different groups of UEs 301 (e.g., enterprise users). For example, individual network slices may deliver different committed service(s) or may be dedicated to a particular customer or enterprise, or both. In this example, each network slice may have different S-NSSAIs with the same SST but with different slice differentiators. Additionally, a single UE may be served with one or more network slice instances simultaneously using a 5G AN, and the UE may be associated with eight different S-NSSAIs. Moreover, an AMF 321 instance serving an individual UE 301 may belong to each of the network slice instances serving that UE.

Network slicing in the NG-RAN 310 involves RAN slice awareness. RAN slice awareness includes differentiated handling of traffic for different network slices, which have been pre-configured. Slice awareness in the NG-RAN 310 is introduced at the PDU session level by indicating the S-NSSAI corresponding to a PDU session in all signaling that includes PDU session resource information. How the NG-RAN 310 supports the slice enabling in terms of NG-RAN functions the set of network functions that comprise each slice) is implementation dependent. The NG-RAN 310 selects the RAN part of the network slice using assistance information provided by the UE 301 or the 5GC 320, which unambiguously identifies one or more of the pre-configured network slices in the PLMN. The NG-RAN 310 also supports resource management and policy enforcement between slices as per SLAs. A single NG-RAN node may support multiple slices, and the NG-RAN 310 may also apply an appropriate RRM policy for the SLA in place to each supported slice. The NG-RAN 310 may also support QoS differentiation within a slice.

The NG-RAN 310 may also use the UE assistance information for the selection of an AMF 321 during an initial attach, if available. The NG-RAN 310 uses the assistance information for routing the initial NAS to an AMF 321. if the NG-RAN 310 is unable to select an AMF 321 using the assistance information, or the UE 301 does not provide any such information, the NG-RAN 310 sends the NAS signaling to a default AMF 321, which may be among a pool of AMFs 321. For subsequent accesses, the UE 301 provides a temp ID, which is assigned to the UE 301 by the 5GC 320, to enable the NG-RAN 310 to route the NAS message to the appropriate AMF 321 as long as the temp ID is valid. The NG-RAN 310 is aware of, and can reach, the AMF 321 that is associated with the temp ID. Otherwise, the method for initial attach applies.

The NG-RAN 310 supports resource isolation between slices. NG-RAN 310 resource isolation may be achieved by means of RRM policies and protection mechanisms that should avoid that shortage of shared resources if one slice breaks the service level agreement for another slice. In some implementations, it is possible to fully dedicate NG-RAN 310 resources to a certain slice. How NG-RAN 310 supports resource isolation is implementation dependent.

Some slices may be available only in part of the network. Awareness in the NG-RAN 310 of the slices supported in the cells of its neighbors may be beneficial for inter-frequency mobility in connected mode. The slice availability may not change within the UE's registration area. The NG-RAN 310 and the 5GC 320 are responsible to handle a service request for a slice that may or may not be available in a given area. Admission or rejection of access to a slice may depend on factors such as support for the slice, availability of resources, support of the requested service by NG-RAN 310.

The UE 301 may be associated with multiple network slices simultaneously. In case the UE 301 is associated with multiple slices simultaneously, only one signaling connection is maintained, and for intra-frequency cell reselection, the UE 301 tries to camp on the best cell. For inter-frequency cell reselection, dedicated priorities can be used to control the frequency on which the UE 301 camps. The 5GC 320 is to validate that the UE 301 has the rights to access a network slice. Prior to receiving an Initial Context Setup Request message, the NG-RAN 310 may be allowed to apply some provisional or local policies based on awareness of a particular slice that the UE 301 is requesting to access. During the initial context setup, the NG-RAN 310 is informed of the slice for which resources are being requested.

FIG. 4 illustrates an example of infrastructure equipment 400. The infrastructure equipment 400 (or “system 400”) may be implemented as a base station, a radio head, a RAN node, such as the RAN nodes 111 or AP 106 shown and described previously, an application server 130, or any other component or device described herein. In other examples, the system 400 can be implemented in or by a UE.

The system 400 includes application circuitry 405, baseband circuitry 410, one or more radio front end modules (RFEMs) 415, memory circuitry 420, power management integrated circuitry (PMIC) 425, power tee circuitry 430, network controller circuitry 435, network interface connector 440, satellite positioning circuitry 445, and user interface circuitry 450. In some implementations, the system 400 may include additional elements such as, for example, memory, storage, a display, a camera, one or more sensors, or an input/output (I/O) interface, or combinations of them, among others. In other examples, the components described with reference to the system 400 may be included in more than one device. For example, the various circuitries may be separately included in more than one device for CRAN, vBBU, or other implementations.

The application circuitry 405 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, one or more of low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD), MultiMediaCard (MMC), Universal Serial Bus (USB) interfaces, Mobile Industry Processor interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports. The processors (or cores) of the application circuitry 405 may be coupled with or may include memory or storage elements and may be configured to execute instructions stored in the memory or storage to enable various applications or operating systems to run on the system 400. In some implementations, the memory or storage elements may include on-chip memory circuitry, which may include any suitable volatile or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, or combinations of them, among other types of memory.

The processor(s) of the application circuitry 405 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSP), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or combinations of them, among others. In some implementations, the application circuitry 405 may include, or may be, a special-purpose processor or controller configured to carry out the various techniques described here. In some implementations, the system 400 may not utilize application circuitry 405, and instead may include a special-purpose processor or controller to process IP data received from an EPC or SGC, for example.

In some implementations, the application circuitry 405 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) or deep learning (DL) accelerators, or both. In some implementations, the programmable processing devices may be one or more a field-programmable devices (FPDs) such as field-programmable gate arrays (FPGAs) and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs) or high-capacity PLDs (HCPLDs); ASICs such as structured ASICs; programmable SoCs (PSoCs), or combinations of them, among others. In such implementations, the circuitry of application circuitry 405 may include logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions described herein. In some implementations, the circuitry of application circuitry 405 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM) or anti-fuses)) used to store logic blocks, logic fabric, data, or other data in look-up-tables (LUTs) and the like.

The baseband circuitry 410 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.

The user interface circuitry 450 may include one or more user interfaces designed to enable user interaction with the system 400 or peripheral component interfaces designed to enable peripheral component interaction with the system 400. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, speakers or other audio emitting devices, microphones, a printer, a scanner, a headset, a display screen or display device, or combinations of them, among others. Peripheral component interfaces may include, but are not limited to, a nonvolatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, among others.

The radio front end modules (RFEMs) 415 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays (see, e.g., antenna array 611 of FIG. 6), and the RFEM may be connected to multiple antennas. In some implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 415, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 420 may include one or more of volatile memory, such as dynamic random access memory (DRAM) or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM), such as high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), or magnetoresistive random access memory (MRAM), or combinations of them, among others. Memory circuitry 420 may be implemented as one or more of solder down packaged integrated circuits, socketed memory modules and plug-in memory cards, for example.

The PMC 425 may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor. The power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over-voltage) conditions. The power tee circuitry 430 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the infrastructure equipment 400 using a single cable.

The network controller circuitry 435 may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to and from the infrastructure equipment 400 using network interface connector 440 using a physical connection, which may be electrical (commonly referred to as a “copper interconnect”), optical, or wireless. The network controller circuitry 435 may include one or more dedicated processors or FPGAs, or both, to communicate using one or more of the aforementioned protocols. In some implementations, the network controller circuitry 435 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

The positioning circuitry 445 includes circuitry to receive and decode signals transmitted or broadcasted by a positioning network of a global navigation satellite system (GNSS). Examples of a GNSS include United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., Navigation with Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbitography and Radio-positioning Integrated by Satellite (DORIS)), among other systems. The positioning circuitry 445 can include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some implementations, the positioning circuitry 445 may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking and estimation without GNSS assistance. The positioning circuitry 445 may also be part of, or interact with, the baseband circuitry 410 or RFEMs 415, or both, to communicate with the nodes and components of the positioning network. The positioning circuitry 445 may also provide data (e.g., position data, time data) to the application circuitry 405, which may use the data to synchronize operations with various infrastructure (e.g., RAN nodes 111).

FIG. 5 illustrates an example of a platform 500 (or “device 500”). In some implementations, the computer platform 500 may be suitable for use as UEs 101, 201, 301, application servers 130, or any other component or device discussed herein. The platform 500 may include any combinations of the components shown in the example. The components of platform 500 (or portions thereof) may be implemented as integrated circuits (ICs), discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination of them adapted in the computer platform 500, or as components otherwise incorporated within a chassis of a larger system. The block diagram of FIG. 5 is intended to show a high level view of components of the platform 500. However, In some implementations, the platform 500 may include fewer, additional, or alternative components, or a different arrangement of the components shown in FIG. 5.

The application circuitry 505 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, RTC, timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as SD MMC or similar, USB interfaces, MIPI interfaces, and JTAG test access ports. The processors (or cores) of the application circuitry 505 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory or storage to enable various applications or operating systems to run on the system 500. In some implementations, the memory or storage elements may be on-chip memory circuitry, which may include any suitable volatile or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, or combinations of them, among other types of memory.

The processor(s) of application circuitry 505 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some implementations, the application circuitry 405 may include, or may be, a special-purpose processor/controller to carry out the techniques described herein. In some implementations, the application circuitry 505 may be a part of a system on a chip (SoC) in which the application circuitry 505 and other components are formed into a single integrated circuit, or a single package.

In some implementations, the application circuitry 505 may include circuitry such as, but not limited to, one or more a field-programmable devices (FPDs) such as FPGAs; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs such as structured ASICs; programmable SoCs (PSoCs), or combinations of them, among others. In some implementations, the application circuitry 505 may include logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions described herein. In some implementations, the application circuitry 505 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), or anti-fuses)) used to store logic blocks, logic fabric, data, or other data in look-up tables (LUTs) and the like.

The baseband circuitry 510 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. The various hardware electronic elements of baseband circuitry 510 are discussed with regard to FIG. 6.

The RFEMs 515 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays (see, e.g., antenna array 611 of FIG. 6), and the RFEM may be connected to multiple antennas. In some implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 515, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 520 may include any number and type of memory devices used to provide for a given amount of system memory. As examples, the memory circuitry 520 may include one or more of volatile memory, such as random access memory (RAM), dynamic RAM (DRAM) or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM), such as high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), or magnetoresistive random access memory (MRAM), or combinations of them, among others. In low power implementations, the memory circuitry 520 may be on-die memory or registers associated with the application circuitry 505. To provide for persistent storage of information such as data, applications, operating systems and so forth, memory circuitry 520 may include one or more mass storage devices, which may include, for example, a solid state drive (SSD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others.

The removable memory circuitry 523 may include devices, circuitry, enclosures, housings, ports or receptacles, among others, used to couple portable data storage devices with the platform 500. These portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards), and USB flash drives, optical discs, or external HDDs, or combinations of them, among others. The platform 500 may also include interface circuitry (not shown) for connecting external devices with the platform 500. The external devices connected to the platform 500 using the interface circuitry include sensor circuitry 521 and electro-mechanical components (EMCs) 522, as well as removable memory devices coupled to removable memory circuitry 523.

The sensor circuitry 521 include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (e.g., sensor data) about the detected events to one or more other devices, modules, or subsystems. Examples of such sensors include inertial measurement units (IMUs) such as accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other audio capture devices, or combinations of them, among others.

The EMCs 522 include devices, modules, or subsystems whose purpose is to enable the platform 500 to change its state, position, or orientation, or move or control a mechanism, system, or subsystem. Additionally, the EMCs 522 may be configured to generate and send messages or signaling to other components of the platform 500 to indicate a current state of the EMCs 522. Examples of the EMCs 522 include one or more power switches, relays, such as electromechanical relays (EMRs) or solid state relays (SSRs), actuators (e.g., valve actuators), an audible sound generator, a visual warning device, motors (e.g., DC motors or stepper motors), wheels, thrusters, propellers, claws, clamps, hooks, or combinations of them, among other electro-mechanical components. in some implementations, the platform 500 is configured to operate one or more EMCs 522 based on one or more captured events, instructions, or control signals received from a service provider or clients, or both.

In some implementations, the interface circuitry may connect the platform 500 with positioning circuitry 545. The positioning circuitry 545 includes circuitry to receive and decode signals transmitted or broadcasted by a positioning network of a GNSS. The positioning circuitry 545 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some implementations, the positioning circuitry 545 may include a Micro-PNT IC that uses a master timing clock to perform position tracking or estimation without GNSS assistance. The positioning circuitry 545 may also be part of, or interact with, the baseband circuitry 410 or RFEMs 515, or both, to communicate with the nodes and components of the positioning network. The positioning circuitry 545 may also provide data (e.g., position data, time data) to the application circuitry 505, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, or the like.

In some implementations, the interface circuitry may connect the platform 500 with Near-Field Communication (NFC) circuitry 540. The NFC circuitry 540 is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, in which magnetic field induction is used to enable communication between NFC circuitry 540 and NFC-enabled devices external to the platform 500 (e.g., an “NFC touchpoint”). The NFC circuitry 540 includes an NFC controller coupled with an antenna element and a processor coupled with the NFC controller. The NFC controller may be a chip or IC providing NFC functionalities to the NFC circuitry 540 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RF signals. The RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 540, or initiate data transfer between the NFC circuitry 540 and another active NFC device (e.g., a smartphone or an NFC-enabled. POS terminal) that is proximate to the platform 500.

The driver circuitry 546 may include software and hardware elements that operate to control particular devices that are embedded in the platform 500, attached to the platform 500, or otherwise communicatively coupled with the platform 500. The driver circuitry 546 may include individual drivers allowing other components of the platform 500 to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform 500. For example, the driver circuitry 546 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform 500, sensor drivers to obtain sensor readings of sensor circuitry 521 and control and allow access to sensor circuitry 521, EMC drivers to obtain actuator positions of the EMCs 522 or control and allow access to the EMCs 522, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 525 (also referred to as “power management circuitry 525”) may manage power provided to various components of the platform 500. In particular, with respect to the baseband circuitry 510, the PMIC 525 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMIC 525 may be included when the platform 500 is capable of being powered by a battery 530, for example, when the device is included in a UE 101, 201, 301.

In some implementations, the PMIC 525 may control, or otherwise be part of, various power saving mechanisms of the platform 500. For example, if the platform 500 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform 500 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform 500 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback or handover. This can allow the platform 500 to enter a very low power state, where it periodically wakes up to listen to the network and then powers down again. In some implementations, the platform 500 may not receive data in the RRC Idle state and instead must transition back to RRC_Connected state to receive data. An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device may be unreachable to the network and may power down completely. Any data sent during this time may incurs a large delay and it is assumed the delay is acceptable.

A battery 530 may power the platform 500, although in some implementations the platform 500 may be deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 530 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, or a lithium-air battery, among others. In some implementations, such as in V2X applications, the battery 530 may be a typical lead-acid automotive battery.

In some implementations, the battery 530 may be a “smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry. The BMS may be included in the platform 500 to track the state of charge (SoCh) of the battery 530. The BMS may be used to monitor other parameters of the battery 530 to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery 530. The BMS may communicate the information of the battery 530 to the application circuitry 505 or other components of the platform 500. The BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry 505 to directly monitor the voltage of the battery 530 or the current flow from the battery 530. The battery parameters may be used to determine actions that the platform 500 may perform, such as transmission frequency, network operation, or sensing frequency, among others.

A power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery 530. In some implementations, the power block 530 may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform 500. In these examples, a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery 530, and thus, the current required. The charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.

The user interface circuitry 550 includes various input/output (I/O) devices present within, or connected to, the platform 500, and includes one or more user interfaces designed to enable user interaction with the platform 500 or peripheral component interfaces designed to enable peripheral component interaction with the platform 500. The user interface circuitry 550 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, or headset, or combinations of them, among others. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other information. Output device circuitry may include any number or combinations of audio or visual display, including one or more simple visual outputs or indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)), multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, or projectors), with the output of characters, graphics, or multimedia objects being generated or produced from the operation of the platform 500. The output device circuitry may also include speakers or other audio emitting devices, or printer(s). In some implementations, the sensor circuitry 521 may be used as the input device circuitry (e.g., an image capture device or motion capture device), and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback). In another example, NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags or connect with another NFC-enabled device. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, or a power supply interface.

FIG. 6 illustrates example components of baseband circuitry 610 and radio front end modules (RFEM) 615. The baseband circuitry 610 can correspond to the baseband circuitry 410 and 510 of FIGS. 4 and 5, respectively. The RFEM 615 can correspond to the RFEM 415 and 515 of FIGS. 4 and 5, respectively. As shown, the RFEMs 615 may include Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, and antenna array 611 coupled together.

The baseband circuitry 610 includes circuitry configured to carry out various radio or network protocol and control functions that enable communication with one or more radio networks using the RF circuitry 606. The radio control functions may include, but are not limited to, signal modulation and demodulation, encoding and decoding, and radio frequency shifting. In some implementations, modulation and demodulation circuitry of the baseband circuitry 610 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping and demapping functionality. In some implementations, encoding and decoding circuitry of the baseband circuitry 610 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder and decoder functionality. Modulation and demodulation and encoder and decoder functionality are not limited to these examples and may include other suitable functionality in other examples. The baseband circuitry 610 is configured to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RE circuitry 606. The baseband circuitry 610 is configured to interface with application circuitry (e.g., the application circuitry 405, 505 shown in FIGS. 4 and 5) for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606. The baseband circuitry 610 may handle various radio control functions.

The aforementioned circuitry and control logic of the baseband circuitry 610 may include one or more single or multi-core processors. For example, the one or more processors may include a 3G baseband processor 604A, a 4G or LTE baseband processor 604B, a 5G or NR baseband processor 604C, or some other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., sixth generation (6G)). In some implementations, some or all of the functionality of baseband processors 604A-D may be included in modules stored in the memory 604G and executed using one or more processors such as a Central Processing Unit (CPU) 604E. in some implementations, some or all of the functionality of baseband processors 604A-D may be provided as hardware accelerators (e.g., FPGAs or ASICs) loaded with the appropriate bit streams or logic blocks stored in respective memory cells. In some implementations, the memory 604G may store program code of a real-time OS (RTOS) which, when executed by the CPU 604E (or other processor), is to cause the CPU 604E (or other processor) to manage resources of the baseband circuitry 610, schedule tasks, or carry out other operations. In some implementations, the baseband circuitry 610 includes one or more audio digital signal processors (DSP) 604F. An audio DSP 604F can include elements for compression and decompression and echo cancellation and may include other suitable processing elements in some implementations.

In some implementations, each of the processors 604A-604E include respective memory interfaces to send and receive data to and from the memory 604G. The baseband circuitry 610 may further include one or more interfaces to communicatively couple to other circuitries or devices, such as an interface to send and receive data to and from memory external to the baseband circuitry 610; an application circuitry interface to send and receive data to and from the application circuitry 405, 505 of FIGS. 4 and 5); an RF circuitry interface to send and receive data to and from RF circuitry 606 of FIG. 6; a wireless hardware connectivity interface to send and receive data to and from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth®/Bluetooth® Low Energy components, Wi-Fi components, and/or the like); and a power management interface to send and receive power or control signals to and from the PMIC 525.

In some implementations (which may be combined with the above described examples), the baseband circuitry 610 includes one or more digital baseband systems, which are coupled with one another using an interconnect subsystem and to a CPU subsystem, an audio subsystem, and an interface subsystem. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem using another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include DSP circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, among other components. In some implementations, the baseband circuitry 610 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry or radio frequency circuitry (e.g., the radio front end modules 615).

In some implementations, the baseband circuitry 610 includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a “multi-protocol baseband processor” or “protocol processing circuitry”) and individual processing device(s) to implement PHY layer functions. In some implementations, the PHY layer functions include the aforementioned radio control functions. In some implementations, the protocol processing circuitry operates or implements various protocol layers or entities of one or more wireless communication protocols. For example, the protocol processing circuitry may operate LTE protocol entities or 5G NR protocol entities, or both, when the baseband circuitry 610 or RF circuitry 606, or both, are part of mmWave communication circuitry or some other suitable cellular communication circuitry. In this example, the protocol processing circuitry can operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In some implementations, the protocol processing circuitry may operate one or more IEEE-based protocols when the baseband circuitry 610 or RF circuitry 606, or both, are part of a Wi-Fi communication system. In this example, the protocol processing circuitry can operate Wi-Fi MAC and logical link control (LLC) functions, The protocol processing circuitry may include one or more memory structures (e.g., 604G) to store program code and data for operating the protocol functions, as well as one or more processing cores to execute the program code and perform various operations using the data. The baseband circuitry 610 may also support radio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry 610 discussed herein may be implemented, for example, as a solder-down substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board or a multi-chip module containing two or more ICs. In some implementations, the components of the baseband circuitry 610 may be suitably combined in a single chip or chipset, or disposed on a same circuit board. In some implementations, some or all of the constituent components of the baseband circuitry 610 and RF circuitry 606 may be implemented together such as, for example, a system on a chip (SoC) or System-in-Package (SiP). In some implementations, some or all of the constituent components of the baseband circuitry 610 may be implemented as a separate SoC that is communicatively coupled with and RF circuitry 606 (or multiple instances of RF circuitry 606). In some implementations, some or all of the constituent components of the baseband circuitry 610 and the application circuitry 405, 505 may be implemented together as individual SoCs mounted to a same circuit board (e.g., a “multi-chip package”).

In some implementations, the baseband circuitry 610 may provide for communication compatible with one or more radio technologies. For example, the baseband circuitry 610 may support communication with an E-UTRAN or other WMAN, a WLAN, or a WPAN. Examples in which the baseband circuitry 610 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

The RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In some implementations, the RF circuitry 606 may include switches, filters, or amplifiers, among other components, to facilitate the communication with the wireless network. The RF circuitry 606 may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 610. The RF circuitry 606 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 610 and provide RF output signals to the FEM circuitry 608 for transmission.

The receive signal path of the RF circuitry 606 includes mixer circuitry 606 a, amplifier circuitry 606 b and filter circuitry 606 c. In some implementations, the transmit signal path of the RF circuitry 606 may include filter circuitry 606 c and mixer circuitry 606 a. The RF circuitry 606 also includes synthesizer circuitry 606 d for synthesizing a frequency for use by the mixer circuitry 606 a of the receive signal path and the transmit signal path. In some implementations, the mixer circuitry 606 a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606 d. The amplifier circuitry 606 b may be configured to amplify the down-converted signals and the filter circuitry 606 c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 610 for further processing. In some implementations, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some implementations, the mixer circuitry 606 a of the receive signal path may comprise passive mixers.

In some implementations, the mixer circuitry 606 a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606 d to generate RF output signals for the FEM circuitry 608. The baseband signals may be provided by the baseband circuitry 610 and may be filtered by filter circuitry 606 c.

In some implementations, the mixer circuitry 606 a of the receive signal path and the mixer circuitry 606 a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some implementations, the mixer circuitry 606 a of the receive signal path and the mixer circuitry 606 a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some implementations, the mixer circuitry 606 a of the receive signal path and the mixer circuitry 606 a of the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some implementations, the mixer circuitry 606 a of the receive signal path and the mixer circuitry 606 a of the transmit signal path may be configured for super-heterodyne operation.

In some implementations, the output baseband signals and the input baseband signals may be analog baseband signals. In some implementations, the output baseband signals and the input baseband signals may be digital baseband signals, and the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 610 may include a digital baseband interface to communicate with the RE circuitry 606. In some dual-mode examples, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the techniques described here are not limited in this respect.

In some implementations, the synthesizer circuitry 606 d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although other types of frequency synthesizers may be used. For example, synthesizer circuitry 606 d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. The synthesizer circuitry 606 d may be configured to synthesize an output frequency for use by the mixer circuitry 606 a of the RF circuitry 606 based on a frequency input and a divider control input. In some implementations, the synthesizer circuitry 606 d may be a fractional N/N+1 synthesizer.

In some implementations, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 610 or the application circuitry 405/505 depending on the desired output frequency. In some implementations, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 405, 505.

The synthesizer circuitry 606 d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some implementations, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some implementations, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some implementations, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. The delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some implementations, synthesizer circuitry 606 d may be configured to generate a carrier frequency as the output frequency, while in other examples, the output frequency may be a multiple of the carrier frequency (e.g,, twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some implementations, the output frequency may be a LO frequency (fLO). In some implementations, the RF circuitry 606 may include an IQ or polar converter.

The FEM circuitry 608 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 611, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing. The FEM circuitry 608 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of antenna elements of antenna array 611. The amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM circuitry 608, or in both the RF circuitry 606 and the FEM circuitry 608.

In some implementations, the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry 608 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 608 may include an LNA to amplify received RF signals and provide the amplified received RE signals as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission by one or more antenna elements of the antenna array 611.

The antenna array 611 comprises one or more antenna elements, each of which is configured convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. For example, digital baseband signals provided by the baseband circuitry 610 is converted into analog RF signals (e.g., modulated waveform) that will be amplified and transmitted using the antenna elements of the antenna array 611 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, directional, or a combination thereof. The antenna elements may be formed in a multitude of arranges as are known and/or discussed herein. The antenna array 611 may comprise microstrip antennas or printed antennas that are fabricated on the surface of one or more printed circuit boards. The antenna array 611 may be formed as a patch of metal foil (e.g., a patch antenna) in a variety of shapes, and may be coupled with the RF circuitry 606 and/or FEM circuitry 608 using metal transmission lines or the like.

Processors of the application circuitry 405/505 and processors of the baseband circuitry 610 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 610, alone or in combination, may execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 405, 505 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., TCP and UDP layers). As referred to herein, Layer 3 may comprise a RRC layer, described in further detail below. As referred to herein, Layer 2 may comprise a MAC layer, an RLC layer, and a PDCP layer, described in further detail below. As referred to herein, Layer 1 may comprise a PHY layer of a UE/RAN node, described in further detail below.

FIG. 7 illustrates example components of communication circuitry 700. In some implementations, the communication circuitry 700 may be implemented as part of the system 400 or the platform 500 shown in FIGS. 4 and 5. The communication circuitry 700 may be communicatively coupled (e.g., directly or indirectly) to one or more antennas, such as antennas 711A, 711B, 711C, and 711D. In some implementations, the communication circuitry 700 includes or is communicatively coupled to dedicated receive chains, processors, or radios, or combinations of them, for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown in FIG. 7, the communication circuitry 700 includes a modem 710 and a modem 720, which may correspond to or be a part of the baseband circuitry 410 and 510 of FIGS. 4 and 5. The modem 710 may be configured for communications according to a first RAT, such as LTE or LTE-A, and the modem 720 may be configured for communications according to a second RAT, such as 5G NR. In some implementations, a processor 705, such as an application processor can interface with the modems 710, 720.

The modem 710 includes one or more processors 712 and a memory 716 in communication with the processors 712. The modem 710 is in communication with a radio frequency (RF) front end 730, which may correspond to or be a part of to the RFEM 415 and 515 of FIGS. 4 and 5. The RF front end 730 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 730 includes RX circuitry 732 and TX circuitry 734. In some implementations, the receive circuitry 732 is in communication with a DL front end 752, which may include circuitry for receiving radio signals from one or more antennas 711A. The transmit circuitry 734 is in communication with a UL front end 754, which is coupled with one or more antennas 711B.

Similarly, the modem 720 includes one or more processors 722 and a memory 726 in communication with the one or more processors 722. The modem 720 is in communication with an RF front end 740, which may correspond to or be a part of to the RFEM 415 and 515 of FIGS. 4 and 5. The RF front end 740 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 740 includes receive circuitry 742 and transmit circuitry 744. In some implementations, the receive circuitry 742 is in communication with a DL front end 760, which may include circuitry for receiving radio signals from one or more antennas 711C. The transmit circuitry 744 is in communication with a UL front end 765, which is coupled with one or more antennas 711D. In some implementations, one or more front-ends can be combined. For example, a RF switch can selectively couple the modems 710, 720 to a single UL front end 772 for transmitting radio signals using one or more antennas.

The modern 710 may include hardware and software components for time division multiplexing UL data (e.g., for NSA NR operations), as well as the various other techniques described herein. The processors 712 may include one or more processing elements configured to implement various features described herein, such as by executing program instructions stored on the memory 716 (e.g., a non-transitory computer-readable memory medium). In some implementations, the processor 712 may be configured as a programmable hardware element, such as a FPGA or an ASIC. In some implementations, the processors 712 may include one or more ICs that are configured to perform the functions of processors 712. For example, each IC may include circuitry configured to perform the functions of processors 712.

The modem 720 may include hardware and software components for time division multiplexing UL data (e.g., for NSA NR operations), as well as the various other techniques described herein. The processors 722 may include one or more processing elements configured to implement various features described herein, such as by executing instructions stored on the memory 726 (e.g., a non-transitory computer-readable memory medium). In some implementations, the processor 722 may be configured as a programmable hardware element, such as a FPGA or an ASIC. In some implementations, the processor 722 may include one or more ICs that are configured to perform the functions of processors 722.

FIG. 8 illustrates various protocol functions that may be implemented in a wireless communication device. In particular, FIG. 8 includes an arrangement 800 showing interconnections between various protocol layers/entities. The following description of FIG. 8 is provided for various protocol layers and entities that operate in conjunction with the 5G NR system standards and the LTE system standards, but some or all of the aspects of FIG. 8 may be applicable to other wireless communication network systems as well.

The protocol layers of arrangement 800 may include one or more of PHY 810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857, in addition to other higher layer functions not illustrated. The protocol layers may include one or more service access points (e.g., items 859, 856, 850, 849, 845, 835, 825, and 815 in FIG. 8) that may provide communication between two or more protocol layers.

The PHY 810 may transmit and receive physical layer signals 805 that may be received from or transmitted to one or more other communication devices. The physical layer signals 805 may include one or more physical channels, such as those discussed herein. The PHY 810 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC 855. The PHY 810 may still further perform error detection on the transport channels, forward error correction (FEC) coding and decoding of the transport channels, modulation and demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and MIMO antenna processing. In some implementations, an instance of 810 may process requests from and provide indications to an instance of MAC 820 using one or more PHY-SAP 815. In some implementations, requests and indications communicated using PHY-SAP 815 may comprise one or more transport channels.

Instance(s) of MAC 820 may process requests from, and provide indications to, an instance of RLC 830 using one or more MAC-SAPS 825. These requests and indications communicated using the MAC-SAP 825 may include one or more logical channels, The MAC 820 may perform mapping between the logical channels and transport channels, multiplexing of MAC SDUs from one or more logical channels onto transport blocks (TBs) to be delivered to 810 using the transport channels, de-multiplexing MAC SDUs to one or more logical channels from TBs delivered from the PHY 810 using transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through HARQ, and logical channel prioritization.

Instance(s) of RLC 830 may process requests from and provide indications to an instance of PDCP 840 using one or more radio link control service access points (RLC-SAP) 835. These requests and indications communicated using RLC-SAP 835 may include one or more RLC channels. The RLC 830 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC 830 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC 830 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

Instance(s) of PDCP 840 may process requests from and provide indications to instance(s) of RRC 855 or instance(s) of SDAP 847, or both, using one or more packet data convergence protocol service access points (MCP-SAP) 845. These requests and indications communicated using PDCP-SAP 845 may include one or more radio bearers. The PDCP 840 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, or integrity verification).

Instance(s) of SDAP 847 may process requests from and provide indications to one or more higher layer protocol entities using one or more SDAP-SAP 849. These requests and indications communicated using SDAP-SAP 849 may include one or more QoS flows. The SDAP 847 may map QoS flows to data radio bearers (DRBs), and vice versa, and may also mark QoS flow identifiers (QFIs) in DL and UL packets. A single SDAP entity 847 may be configured for an individual PDU session. In the UL direction, the NG-RAN 110 may control the mapping of QoS Flows to DRB(s) in two different ways, reflective mapping or explicit mapping. For reflective mapping, the SDAP 847 of a UE 101 may monitor the QFIs of the DL packets for each DRB, and may apply the same mapping for packets flowing in the UL, direction. For a DRB, the SDAP 847 of the UE 101 may map the UL packets belonging to the QoS flows(s) corresponding to the QoS flow ID(s) and PDU session observed in the DL packets for that DRB. To enable reflective mapping, the NG-RAN 310 may mark DL packets over the Uu interface with a QoS flow ID. The explicit mapping may involve the RRC 855 configuring the SDAP 847 with an explicit QoS flow to DRB mapping rule, which may be stored and followed by the SDAP 847. In some implementations, the SDAP 847 may only be used in NR implementations and may not be used in LTE implementations.

The RRC 855 may configure, using one or more management service access points (M-SAP), aspects of one or more protocol layers, which may include one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840 and SDAP 847. In some implementations, an instance of RRC 855 may process requests from and provide indications to one or more NAS entities 857 using one or more RRC-SAPS 856. The main services and functions of the RRC 855 may include broadcast of system information (e.g., included in master information blocks (MIBs) or system information blocks (SIBs) related to the NAS), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE 101 and RAN 110 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. The MIBs and SIBs may comprise one or more information elements, which may each comprise individual data fields or data structures.

The NAS 857 may form the highest stratum of the control plane between the UE 101 and the AMF 321. The NAS 857 may support the mobility of the UEs 101 and the session management procedures to establish and maintain IP connectivity between the UE 101 and a P-GW in LTE systems.

In some implementations, one or more protocol entities of arrangement 800 may be implemented in UEs 101, RAN nodes 111, AMF 321 in NR implementations or MME 22.1 in LTE implementations, UPF 302 in NR implementations or S-GW 222 and P-GW 223 in LTE implementations, or the like to be used for control plane or user plane communications protocol stack between the aforementioned devices. In some implementations, one or more protocol entities that may be implemented in one or more of UE 101, gNB 111, AMF 321, among others, may communicate with a respective peer protocol entity that may be implemented in or on another device using the services of respective lower layer protocol entities to perform such communication. In some implementations, a gNB-CU of the gNB 111 may host the RRC 855, SDAP 847, and PDCP 840 of the gNB that controls the operation of one or more gNB-DUs, and the gNB-DUs of the gNB 111 may each host the RLC 830, MAC 820, and PHY 810 of the gNB 111.

In some implementations, a control plane protocol stack may include, in order from highest layer to lowest layer, NAS 857, RRC 855, PDCP 840, RLC 830, MAC 820, and PHY 810. In this example, upper layers 860 may be built on top of the NAS 857, which includes an IP layer 861, an SCTP 862, and an application layer signaling protocol (AP) 863.

In some implementations, such as NR implementations, the AP 863 may be an NG application protocol layer (NGAP or NG-AP) 863 for the NG interface 113 defined between the NG-RAN node 111 and the AMF 321, or the AP 863 may be an Xn application protocol layer (XnAP or Xn-AP) 863 for the Xn interface 112 that is defined between two or more RAN nodes 111.

The NG-AP 863 may support the functions of the NG interface 113 and may comprise elementary procedures (EPs). An NG-AP EP may be a unit of interaction between the NG-RAN node 111 and the AMF 321. The NG-AP 863 services may include two groups: UE-associated services (e.g., services related to a UE 101) and non-UE-associated services (e.g., services related to the whole NG interface instance between the NG-RAN node 111 and AMF 321). These services may include functions such as, but not limited to: a paging function for the sending of paging requests to NG-RAN nodes 111 involved in a particular paging area; a UE context management function for allowing the AMF 321 to establish, modify, or release a UE context in the AMF 321 and the NG-RAN node 111; a mobility function for UEs 101 in ECM-CONNECTED mode for intra-system HOs to support mobility within NG-RAN and inter-system to support mobility from/to EPS systems; a NAS Signaling Transport function for transporting or rerouting NAS messages between UE 101 and AMF 321; a NAS node selection function for determining an association between the AMF 321 and the UE 101; NG interface management function(s) for setting up the NG interface and monitoring for errors over the NG interface; a warning message transmission function for providing means to transfer warning messages using NG interface or cancel ongoing broadcast of warning messages; a configuration transfer function for requesting and transferring of RAN configuration information (e.g., SON information or performance measurement (PM) data) between two RAN nodes 111 using CN 120, or combinations of them, among others.

The XnAP 863 may support the functions of the Xn interface 112 and may comprise XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may comprise procedures used to handle UE mobility within the NG RAN 111 (or E-UTRAN 210), such as handover preparation and cancellation procedures, SN Status Transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, or dual connectivity related procedures, among others. The XnAP global procedures may comprise procedures that are not related to a specific UE 101, such as Xn interface setup and reset procedures, NG-RAN update procedures, or cell activation procedures, among others.

In LTE implementations, the AP 863 may be an S1 Application Protocol layer (S1-AP) 863 for the S1 interface 113 defined between an E-UTRAN node 111 and an MME, or the AP 863 may be an X2 application protocol layer (X2AP or X2-AP) 863 for the X2 interface 112 that is defined between two or more E-UTRAN nodes 111.

The S1 Application Protocol layer (S1-AP) 863 may support the functions of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include S1-AP EPs. An S1-AP EP may be a unit of interaction between the E-UTRAN node 111 and an MME 221within an LTE CN 120. The S1-AP 863 services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.

The X2AP 863 may support the functions of the X2 interface 112 and may include X2AP basic mobility procedures and X2AP global procedures. The X2AP basic mobility procedures may include procedures used to handle UE mobility within the E-UTRAN 120, such as handover preparation and cancellation procedures, SN Status Transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, or dual connectivity related procedures, among others. The X2AP global procedures may comprise procedures that are not related to a specific UE 101, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, or cell activation procedures, among others.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 862 may provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). The SCTP 862 may ensure reliable delivery of signaling messages between the RAN node 111 and the AMF 321/MME 221 based in part on the IP protocol, supported by the IP 861. The Internet Protocol layer (IP) 861 may be used to perform packet addressing and routing functionality. In some implementations the IP layer 861 may use point-to-point transmission to deliver and convey PDUs. In this regard, the RAN node 111 may include L2 and L1 layer communication links (e.g., wired or wireless) with the MME/AMF to exchange information.

In some implementations, a user plane protocol stack may include, in order from highest layer to lowest layer, SDAP 847, PDCP 840, RLC 830, MAC 820, and PHY 810. The user plane protocol stack may be used for communication between the UE 101, the RAN node 111, and UPF 302 in NR implementations or an S-GW 222 and P-GW 223 in LTE implementations. In this example, upper layers 851 may be built on top of the SDAP 847, and may include a user datagram protocol (UDP) and IP security layer (UDP/IP) 852, a General Packet Radio Service (GPRS) Tunneling Protocol for the user plane layer (GTP-U) 853, and a User Plane PDU layer (UP PDU) 863.

The transport network layer 854 (also referred to as a “transport layer”) may be built on IP transport, and the GTP-U 853 may be used on top of the UDP/IP layer 852 (comprising a UDP layer and IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also referred to as the “Internet layer”) may be used to perform packet addressing and routing functionality. The IP layer may assign IP addresses to user data packets in any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 853 may be used for carrying user data within the GPRS core network and between the radio access network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example. The UDP/IP 852 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node 111 and the S-GW 222 may utilize an S1-U interface to exchange user plane data using a protocol stack comprising an L1 layer (e.g., PHY 810), an L2 layer (e.g., MAC 820, RLC 830, PDCP 840, and/or SDAP 847), the UDP/IP layer 852, and the GTP-U 853. The S-GW 222 and the P-GW 223 may utilize an S5/S8 a interface to exchange user plane data using a protocol stack comprising an L1 layer, an L2 layer, the UDP/IP layer 852, and the GTP-U 853. As discussed previously, NAS protocols may support the mobility of the UE 101 and the session management procedures to establish and maintain IP connectivity between the UE 101 and the P-GW 223.

Moreover, although not shown by FIG. 8, an application layer may be present above the AP 863 and/or the transport network layer 854. The application layer may be a layer in which a user of the LE 101, RAN node 111, or other network element interacts with software applications being executed, for example, by application circuitry 405 or application circuitry 505, respectively. The application layer may also provide one or more interfaces for software applications to interact with communications systems of the LIE 101 or RAN node 111, such as the baseband circuitry 610. In some implementations, the IP layer or the application layer, or both, may provide the same or similar functionality as layers 5-7, or portions thereof, of the Open Systems Interconnection (OSI) model (e.g., OSI Layer 7—the application layer, OSI Layer 6—the presentation layer, and OSI Layer 5—the session layer).

NFV architectures and infrastructures may be used to virtualize one or more NFs, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components and functions.

FIG. 9 illustrates a block diagram of example of a computer system that includes components for reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the techniques described herein. In this example, FIG. 9 shows a diagrammatic representation of hardware resources 900 including one or more processors (or processor cores) 910, one or more memory or storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled using a bus 940. For implementations where node virtualization (e.g., NFV) is utilized, a hypervisor 902 may be executed to provide an execution environment for one or more network slices or sub-slices to utilize the hardware resources 900.

The processors 910 may include a processor 912 and a processor 914. The processor(s) 910 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The memory/storage devices 920 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 920 may include, but are not limited to, any type of volatile or nonvolatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, or solid-state storage, or combinations of them, among others.

The communication resources 930 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 904 or one or more databases 906 using a network 908. For example, the communication resources 930 may include wired communication components (e.g., for coupling using USB), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi components, and other communication components.

Instructions 950 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 910 to perform any one or more of the methodologies discussed herein. The instructions 950 may reside, completely or partially, within at least one of the processors 910 (e.g., within the processor's cache memory), the memory/storage devices 920, or any suitable combination thereof. Furthermore, any portion of the instructions 950 may be transferred to the hardware resources 900 from any combination of the peripheral devices 904 or the databases 906. Accordingly, the memory of processors 910, the memory/storage devices 920, the peripheral devices 904, and the databases 906 are examples of computer-readable and machine-readable media.

For next generation systems, such as NR, high frequency band communication has attracted significantly attention from the industry, since it can provide wider bandwidth to support the future integrated communication system. The beam forming is an important critical technology for the implementation of high frequency band system due to the fact that the beam forming gain can compensate the severe path loss caused by atmospheric attenuation, improve the SNR, and enlarge the coverage area. By aligning the transmission beam to the target UE, radiated energy is focused for higher energy efficiency, and mutual UE interference is suppressed.

In NR, uplink control information (UCI) can be carried by uplink channels such as PUCCH or PUSCH transmitted by the UE. In particular, UCI can include scheduling request (SR), hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback, channel state information (CSI) report, e.g., channel quality indicator (CQI), pre-coding matrix indicator (PMI), CSI resource indicator (CRI) and rank indicator (RI) and/or beam related information (e.g., L1-RSRP (layer 1-reference signal received power)).

FIG. 10 illustrates a flowchart of an example uplink communication process 1001. This process 1001 can be performed by a UE. At 1005, the UE receives, from one or more TRPs, a PDSCH transmission. In some implementations, receiving the PDSCH transmission can include receiving transmissions from multiple TRPs. At 1010, the UE determines, for a PUCCH carrying HARQ-ACK, a TRP index in accordance with a CORESET scheduling the PDSCH transmission. In some implementations, one or more DCI messages carried by PDCCH within one or more CORESETs can provide information regarding the scheduling of the PDSCH transmission. In some implementations, the TRP index is indicated by a ConfiguredGrantConfig information element provided by a RRC layer. At 1015, the UE transmits, via the PUCCH, HARQ-ACK information based on the receiving of the PDSCH transmission in accordance with the TRP index.

Multiple CORESETs can be associated with a PDSCH transmission. For example, the PDSCH transmission can be scheduled by a group of CORESETS including a first CORESET and a second CORESET. The first CORESET can be associated with the first index value. The second CORESET can be associated with a second index value. The TRP index can include the first index value. Determining the TRP index, at 1010, can include determining the first index value associated with the first CORESET and determining a second index value associated with the second CORESET. Determining the first index can include using a CORESET index parameter configured by a RRC layer. Determining the first index value can include using a default value for the first index value based on the first index value not being provided by a network.

Transmitting the HARQ-ACK information, at 1015, can be responsive to the first index value and the second index value. In some implementations, transmitting the HARQ-ACK information can include transmitting first HARQ-ACK information associated with the first CORESET and second HARQ-ACK information associated with the second CORESET. Transmitting the HARQ-ACK information can include using the first index value and the second index value for HARQ-ACK codebook construction. For example, the HARQ-ACK feedback can be encoded for transmission based on a codebook selected based on inputs including the first and second index values.

FIG. 11 illustrates a diagram of an example wireless communication system 1101 that includes multiple RAN nodes 1105 a-b that are TRPs. The system 1001 can be based on NW The RAN nodes 1010 a-b can individually or jointly transmit or receive control and data channels to or from a UE 1120. The nodes 1010 a-b can be configured as TRPs. In a multi-TRP operation, for example, the RAN nodes 1010 a-b can transmit data to a UE 1120 at the same time. In some implementations, the UE 1120 can be equipped with two or multiple sub-arrays or panels, and the UE can transmit or receive control and data channels using two or more panels simultaneously to improve the link budget. In this example, the UE 1120 is configured to form two Tx or Rx beams at the same time for the transmission or reception of physical channels, signals, or both.

In some implementations, a PUCCH transmission overlaps a PUSCH transmission in time in a slot in a PUCCH group. in such implementations, the UE can multiplex UCI on PUSCH and drops PUCCH if a timeline requirement is satisfied. One example of a relevant timeline requirement is given by Section 9.2.5 in 3GPP TS 38.213 V15.5.0, “NR: Physical layer procedures for control.” Others are possible.

For multi-TRP operation, when a PUCCH transmission which is triggered or configured from a first TRP, e.g., node 1105 a, overlaps with a PUSCH transmission which is triggered or configured from a second TRP, e.g., 1105 b, if a timeline requirement is satisfied, the UE 1120 may not be able to multiplex UCI from the first TRP on PUSCH from the second TRP. More specifically, if two TRPs have loose coordination, e.g., non-ideal backhaul, the second TRP may not know the configuration or resource allocation of the UCI in the first TRP, and thus may not decode the UCI and uplink data on PUSCH correctly. A UE can be configured to handle cases where uplink channels such as PUCCH and PUSCH overlap in multi-TRP operations.

For multi-TRP operation, when a PUCCH transmission which is triggered or configured from a first TRP overlaps with a PUSCH transmission which is triggered or configured from a second TRP, if a timeline requirement is satisfied, UE may not be able to multiplex UCI from the first TRP on PUSCH from the second TRP. More specifically, if two TRPs have loose coordination, e.g., non-ideal backhaul, the second TRP may not know the configuration or resource allocation of the UCI in the first TRP, and thus may not decode the UCI and uplink data on PUSCH correctly. To address this issue, certain enhancements on handling overlapping of PUCCH and PUSCH in the case of multi-TRP operations can be considered.

A technique for handling overlapping of PUCCH and PUSCH for multi-TRP operation can include, within a PUCCH group, when a PUCCH transmission which is configured or triggered by a first TRP overlaps a PUSCH transmission in a slot which is configured or triggered by a second TRP, if the time requirement is satisfied, UE transmits one of the PUCCH and PUSCH and drops the other. A dropping determination can be based on a dropping rule. A dropping rule, for example, can depend on the timing of a PUCCH and PUSCH transmission or a carrier index if PUCCH and PUSCH are scheduled in a different component carrier or associated TRP index (for example, TRPs can be ordered within a component carrier) for the PUCCH and PUSCH transmission or a combination thereof.

In some implementations, UE can drop one of the PUCCH transmission or PUSCH transmission which is targeted for different TRPs with the earlier or later transmission timing and transmit another. For instance, if PUCCH is scheduled and configured earlier than PUSCH, PUCCH can be transmitted and PUSCH can be dropped. Further, if these two channels are configured and scheduled with the same starting symbol, the dropping rule can depend on the last symbol of these two channels.

FIG. 12 illustrates an example of a transmission timing based dropping rule. The PUCCH and PUSCH scheduled transmissions overlap in the same slot. In the example, PUCCH for TRP #0 is dropped (illustrated by a cross-out) as it is configured and/or scheduled later than PUSCH for TRP #1. As such, the UE transmits the PUSCH for TRP #1.

In another example, UE may drop one of the PUCCH and PUSCH channels with the highest TRP index and transmit another with the lowest TRP index or vice versa. For instance, within a PUCCH group, when a PUCCH transmission which is configured or triggered by TRP #0 overlaps a PUSCH transmission in a slot which is configured or triggered by TRP #1, if the time requirement is satisfied, UE transmits the PUCCH for TRP #0 and drops PUSCH for TRP #1.

FIG. 13 illustrates an example of a dropping rule based on a TRP index. The PUCCH and PUSCH scheduled transmissions overlap in the same slot. In the example, PUSCH for TRP #1 is dropped (illustrated by a cross-out) because it has the highest TRP index. Thus, PUCCH for TRP #0 (the lowest TRP index) is transmitted.

In some implementations, within a PUCCH group, when a PUCCH which is configured or triggered by a first TRP overlaps two transmissions in a slot which are configured or triggered by first and second TRPs, respectively, if the timeline requirement is satisfied, UE multiplexes UCI on PUSCH with the same TRP index. If these two PUSCHs are not overlapping in time in a slot, or these two PUSCHs are configured or scheduled in a different CC, UE may transmit these two PUSCHs and UCI is multiplexed on PUSCH for the first TRP.

A UE can be configured to multiplex UCI based on a TRP index. In some implementations, if a UE transmits multiple PUSCHs in a slot on respective serving cells and the UE would multiplex UCI in one of the multiple PUSCHs and the UE does not multiplex aperiodic CSI in any of the multiple PUSCHs, the UE can be configured to multiplex the UCI in a PUSCH associated with a same TRP index of the serving cell with the smallest ServCell Index. This can be subject to the conditions in Subclause 9.2.5 of 3GPP TS 38.213 for UCI multiplexing. If the UE transmits more than one PUSCHs in the slot on the serving cell with the smallest ServCell Index that fulfil the conditions in Subclause 9.2.5 for UCI multiplexing, the UE can be configured to multiplex the UCI in the earliest PUSCH associated with a same TRP index that the UE transmits in the slot.

FIG. 14 illustrates an example of a multiplexing rule for when PUCCH overlaps with two PUSCHs within a PUCCH group. In this example, PUCCH for TRP #1 is dropped (illustrated by a cross-out) and UCI is multiplexed on PUSCH with the same TRP index (TRP #1). In some implementations, UCI can be multiplexed on PUSCH with the lowest Component Carrier (CC) index (on CC #0 or PUSCH with TRP #0).

FIG. 15 illustrates another example of a multiplexing rule for when PUCCH overlaps with two PUSCHs within a PUCCH group. In the example, PUCCH for TRP #1 is dropped (illustrated by a cross-out) and UCI is multiplexed on PUSCH with the same TRP index (TRP #1). In some implementations, UCI can be multiplexed on the PUSCH with earliest starting symbol (PUSCH with TRP #0).

FIG. 16 illustrates another example of a multiplexing rule for when PUCCH overlaps with two PUSCHs within a PUCCH group. The PUCCH (TRP #1) overlaps two PUSCHs including a dynamic grant PUSCH (TRP #0) and a configured grant PUSCH (TRP #1). In the example, PUCCH for TRP #1 is dropped and UCI is multiplexed on the configured grant PUSCH with the same TRP index (TRP #1). In some implementations, UCI can be multiplexed on a dynamic grant PUSCH (PUSCH with TRP #0).

In some implementations, the dropping rule or multiplexing rule on handling overlapping of one or more PUCCHs, one or more PUSCHs, or both can be applied for the case when the one or more PUCCHs, the one or more PUSCHs, or both are associated with the same TRP index. In some implementations, within a PUCCH group, when one or more PUCCH transmissions which are configured or triggered by one or more TRPs overlaps one or more PUSCH transmissions in a slot which are configured or triggered by one or more TRPs, if a time requirement is satisfied, the LE can be configured to multiplex UCI on PUSCH having the same TRP index. If the PUSCHs for one or more TRPs do not overlap in time in a slot in a CC, UE can be configured to transmit one or more PUSCHs for these TRPs, otherwise, the UE can be configured to drop one of the PUSCHs in accordance with a dropping rule.

FIG. 17 illustrates an example of a multiplexing rule when two PUCCHs overlap with two PUSCHs. In the example, UCI is multiplexed on PUSCH with the same TRP index. Given that PUSCHs for these two TRPs do not overlap in time, UE transmits these two PUSCH to the corresponding TRPs, respectively.

In some implementations, within a PUCCH group, when one or more PUCCH transmissions which are configured or triggered by one or more TRPs overlap one or more PUSCH transmissions in a slot which are configured or triggered by one or more TRPs, if a time requirement is satisfied, a UE can be configured to apply a dropping rule on the overlapping PUCCH and PUSCHs from different TRPs. In some implementations, the UE can be configured to multiplex the UCI on PUSCH with the same TRP index if the resulting PUCCH and PUSCH for the same TRP overlap in time in a slot within a PUCCH group.

For uplink transmissions, a UE can determine a TRP index based on CORESET scheduling information. In some implementations, for a PUCCH carrying dynamic HARQ-ACK, a TRP index can be implicitly derived in accordance with one or more CORESETs scheduling a corresponding PDSCH transmission. In some implementations, a CORESET index parameter can indicate the TRP index for a CORESET. The CORESET index parameter can be configured by a RRC layer. In some implementations, for a PUCCH carrying a CSI report, SR, and semi-persistent HARQ-ACK feedback, a TRP index can be derived in accordance with a PUCCH resource configuration, e.g., one PUCCH resource or PUCCH resource set or PUCCH configuration is associated with one TRP index.

In some implementations, a multiplexing rule or dropping rule can depend on whether the PUCCH and PUSCH are scheduled from the same or different CORESETs. For instance, when the CORESET used to schedule the PDSCH (and corresponding HARQ-ACK feedback carried by PUCCH) and PUSCH is the same, and if the PUCCH and PUSCH overlap in time in a slot within a PUCCH group, UE can multiplex the UCI on PUSCH and drops the PUCCH. In some implementations, a UE can perform multiplexing assuming the same TRP.

When the CORESETs used to schedule the PDSCH (and corresponding HARQ-ACK feedback carried by PUCCH) and PUSCH are different, and if the PUCCH and PUSCH overlap in time in a slot within a PUCCH group, UE may apply the aforementioned dropping rule, :In some implementations, UE can perform dropping assuming different TRPs.

In the case when separate HARQ-ACK codebooks, targeting different TRPs, are defined, a first HARQ-ACK codebook can correspond to the HARQ-ACK codebook which is scheduled by the CORESET with the lowest index and the second HARQ-ACK codebook can correspond to the HARQ-ACK codebook which is scheduled by the CORESET with the next lowest index.

One or more parameters associated to a CORESET configuration can be used to identify an association to respective CORESETs. In some implementations, for an overlap between two UL channels, triggered by DCIs in CORESETs with different indices may target the same TRP, and can be multiplexed. In such cases, the one or more parameters to identify TRPS can be used to determine the UE behavior. Examples of parameters such as id-1, id-2, etc. are further discussed below. In some implementations, a CORESET index to TRP index mapping can be defined, and in such cases, the CORESET index can be used to determine the target TRP, and thereby, the multiplexing and/or dropping behavior.

For semi-persistent PUSCH transmission and corresponding semi-persistent HARQ-ACK feedback, TRP index can be derived in accordance with a CORESET scheduling the initial transmission. In some implementations, the TRP index can be included in the SPS-Config structure which provides a UE with Semi-Persistent Scheduling (SPS) configuration information. This can apply for the initial or subsequent transmission. In some implementations, the SPS-Config structure can be based on Section 6.3.2 in 3GPP TS 38.331 V15.5.0, “NR: Radio Resource Control (RRC) protocol specification.” Other versions or standards are possible. In addition to providing SPS-related information such as periodicity, HARD processes, modulation, a SPS-Config structure can be modified to include a TRP index. In some implementations, the TRP index is a two-integer-value field, e.g., 0 or 1.

For PUSCH which is dynamically scheduled, e.g., scheduled by DCI format 0_0 or 0_1 or the initial transmission which is activated from a Type 2 configured grant PUSCH, a TRP index can be derived in accordance with a CORESET scheduling the corresponding PUSCH transmission. For Type 1 configured grant PUSCH, a TRP index can be included in ConfiguredGrantConfig For Type 2 configuration grant PUSCH transmission which is not the initial transmission, in some implementations, a TRP index can be based on the TRP index from the initial transmission, e.g., in accordance with CORESET scheduling initial transmission. In some implementations, a TRP index can be derived from the TRP index from ConfiguredGrantConfig.

In some implementations, for PUSCH which is dynamically scheduled by DCI format 0_1 or based on a configured grant, a TRP index can be derived from the TRP index configured for an associated SRS indicated by DCI or configured by higher layer signaling. For PUSCH which is dynamically scheduled by DCI format 0_0, a TRP index can be derived from the PUCCH resource with lowest resource ID in an active bandwidth part.

A TRP index for uplink transmission, in some implementations, can be configured in or associated with a spatial relation information. As such, a UE can be configured to determine the associated TRP index for an uplink channel such as PUSCH or PUCCH by RRC signaling. RRC signaling can include providing a TRP index in a ConfiguredGrantConfig structure. In some implementations, the ConfiguredGrantConfig can include a trpIndex parameter, frequencyHopping parameter, cg-DMRS-Configuration parameter, a mcs-Table parameter, a resourceAllocation parameter, and others. More, less, or different parameters are possible. The trpIndex parameter can be an integer, e.g., INTEGER(0,1). The frequencyHopping parameter can specify, if present, whether frequency hopping is performed intraslot or interslot. The cg-DMRS-Configuration parameter can include DMRS-UplinkConfig. The mcs-Table parameter can specify a modulation type, e.g., QAM 256, QAM 64 Low SE, etc.

Further, for transmitting a semi-persistent CSI report on PUSCCH or PUSCH, a TRP index can be configured within semiPersistentOnPUCCH or semiPersistentOnPUSCH which can be based on Section 6.3.2 in TS 38.331. In some implementations, the semiPersistentOnPUCCH can include a trpIndex parameter, reportSlotConfig parameter to specify CSI-ReportPeriodicityAndOffset, and a pucch-CSI-ResourceList parameter which is a sequence of PUCCH-CShResource. More, less, or different parameters are possible. The semiPersistentOnPUSCH can include trpIndex parameter, reportSlotConfig parameter to specify a slot configuration, reportSlotOffsetList parameter to specify a list of one or more slot offset values, and a p0alpha parameter to specify a PUSCH AlphaSetId.

An uplink channel associated with the same TRP index can indicate the uplink channel transmitted based on the same Radio Network Temporary ID (RNTI), or from the same antenna port(s) or antenna port(s) group or panel, or share the same subset of or all parameters in a PUSCH-Config or PUCCH-Config, or be configured in a PUSCH-Config or PUCCH-Config. In some implementations, the parameter trpIndex can indicate a transmission entity index.

Some techniques can associate different UL channel transmissions to the respective TRPs. This can be useful for deployments relying heavily on beamformed transmission and/or reception, and especially using relatively narrow spatial beams. However, there can be cases with an ideal backhaul between TRPs, where UL channels transmitted from the UE can be received reliably at multiple TRPs or sufficient to be received at one of the TRPs. In such cases, a UCI targeting TRP #2 can be multiplexed within a PUSCH targeted for TRP #1, and vice versa. The association to a particular TRP can still exist based on the CORESET in which the triggering DCI was found or based on higher layer association for periodic and semi-persistent transmissions or transmission occasions. In some implementations, the UCI can be multiplexed in the PUSCH although they can be associated with different TRPs. In some implementations, a UE can be configured by one or more higher layers to (1) multiplex between UCI or between UCI and PUSCH even if these are associated with different TRPs, or, (2) multiplex between UCI or between UCI and PUSCH when these are associated with same TRPs.

In some implementations, the network (NW) can associate an index, e.g., id-1 (which can have 0 or 1 value), to each CORESET associated with an active BWP for each CC. This can partition all CORESETs associated with an active BWP in all CCs into two partitions. CORESET #0 can be associated with id-1=0. In some implementations, by default if not signaled in a CC, CORESETs in an active BWP are associated with an id-1=0. This association can be used for grouping a PDSCH for HARQ-ACK codebook construction within a PUCCH-group. In some implementations, the id-1 value corresponds to a CORESET pool index, which can be configured by RRC.

In some implementations, the NW can associate an index, e.g., id-2 (which can value 0 or 1), to each PUCCH-Resource or each PUCCH-ResourceSet configured to a UE (PUCCH-Config) for each CC in a PUCCH group. This includes resources for periodic, semi-persistent CSI reporting. In some implementations, default PUCCH-ResourceSets are associated with id-2=0. By default (if not signaled in a CC), PUCCH-Resource is associated with an id-2=0. This can enable a UE to multiplex UCI associated with the same id-2 value. This can enable a UE to prioritize UCI associated with different id-2 values.

In some implementations, if a UE is configured with id-1=0,1 and id-2=0,1, then id-1=0,1 is associated with id-2=0,1 respectively. This implies that a UCI in response to DCI associated with id-1=0,1 is carried by PUCCH-Resource/PUCCH-ResourceSets associated with id-2=0,1 respectively. After this association, a particular PUCCH resource (within that partition) can be selected by PRI. In particular, HARQ-ACK based on PDSCH group associated with id-1=0,1 is carried by PUCCH-Resource/PUCCH-ResourceSets associated with id-2=0,1 respectively. In some implementations, if a UE is configured with id-1=0,1 and id-2=0 only then id-1=0,1 is associated with id-2=0. This implies that HARQ-ACK feedback is generated separately based on PDSCH group associated with id-1=0 or 1. However, there is no partitioning of PUCCH resources and a particular PUCCH from all PUCCH resources selected by PRI.

Associations, such as id-1 and id-2, can be signaled using RRC signaling. The associations can be signaled in each CC. In some implementations, associations, such as id-1 and id-2, can be signaled using a medium access control (MAC) control element (CE) (MAC CE).

A technique performed by a UE for wireless communications can include determining a PUCCH carrying HARQ-ACK overlaps a PUSCH in a slot in a PUCCH group; multiplexing the HARQ-ACK on the PUSCH when the PUCCH and PUSCH are scheduled by PDSCH in a same CORESET; and dropping the PUCCH transmission. In some implementations, within a PUCCH group, when a PUCCH transmission which is configured or triggered by a first TRP overlaps a PUSCH transmission in a slot which is configured or triggered by a second TRP, if the time requirement is satisfied, UE transmits one of the PUCCH and PUSCH and drops the other. Dropping a UL transmission can be based on a dropping rule. In some implementations, a dropping rule may depend on the timing of PUCCH and PUSCH transmission or carrier index if PUCCH and PUSCH are scheduled in a different component carrier or associated TRP index for the PUCCH and PUSCH transmission or a combination thereof.

In some implementations, within a PUCCH group, when a PUCCH which is configured or triggered by a first TRP overlaps two PUSCH transmissions in a slot which are configured or triggered by first and second TRPs, respectively, if the timeline requirement is satisfied, UE multiplexes UCI on PUSCH with the same TRP index. In some implementations, if these two PUSCHs are not overlapping in time in a slot, or these two PUSCHs are configured or scheduled in a different CC, UE may transmit these two PUSCHs and the UCI is multiplexed on PUSCH for the first TRP.

A dropping rule or multiplexing rule on handling overlapping of one or more PUCCHs and/or one or more PUSCHs can be applied for the case when the one or PUCCHs and/or the one or more PUSCHs are associated with a same TRP index. In some implementations, within a PUCCH group, when one or more PUCCH transmissions which are configured or triggered by one or more TRPs overlaps one or more PUSCH transmissions in a slot which are configured or triggered by one or more TRPs, if the time requirement is satisfied, UE first multiplexes UCI on PUSCH with same TRP index. In some implementations, if the PUSCHs for one or more TRPs do not overlap in time in a slot in a CC, HE transmits one or more PUSCHs for these TRPs, otherwise, UE may drop one of the PUSCHs in accordance with the aforementioned dropping rule.

In some implementations, within a PUCCH group, when one or more PUCCH transmissions which are configured or triggered by one or more TRPs overlaps one or more PUSCH transmissions in a slot which are configured or triggered by one or more TRPs, if the time requirement is satisfied, UE first applies a dropping rule on the overlapping PUCCH and PUSCHs from different TRPs; wherein UE multiplexes the UCI on PUSCH with the same TRP index if the resulting PUCCH and PUSCH for the same TRP overlap in time in a slot within a PUCCH group.

In some implementations, for PUCCH carrying dynamic HARQ-ACK, TRP index can be implicitly derived in accordance with control resource set (CORESET) scheduling the corresponding PDSCH transmission. In some implementations, a multiplexing rule or dropping rule may depend on whether the PUCCH and PUSCH are scheduled from same or different CORESETs. In some implementations, when the CORESET used to schedule the PDSCH (and corresponding HARQ-ACK feedback carried by PUCCH) and PUSCH is the same, and if the PUCCH and PUSCH overlap in time in a slot within a PUCCH group, UE may multiplex the UCI on PUSCH and drops the PUCCH.

In some implementations, when the CORESETs used to schedule the PDSCH (and corresponding HARQ-ACK feedback carried by PUCCH) and PUSCH are different, and if the PUCCH and PUSCH overlap in time in a slot within a PUCCH group, UE may apply a dropping rule. In some implementations, in case when a joint HARQ-ACK codebook is defined, the first HARQ-ACK codebook may correspond to the HARQ-ACK codebook which is scheduled by the CORESET with lowest index and the second HARQ-ACK codebook may correspond to the HARQ-ACK codebook which is scheduled by the CORESET with the next lowest index.

A TRP can be determined based on a UL grant configuration. In some implementations, for Type 1 configured grant PUSCH, TRP index can be included in ConfiguredGrantConfig. In some implementations, for Type 2 configuration grant PUSCH transmission which is not the initial transmission, TRP index can be based on the TRP index from the initial transmission, e.g., in accordance with CORESET scheduling initial transmission or derived from the TRP index from ConfiguredGrantConfig.

In some implementations, for PUSCH which is dynamically scheduled by DCI format 0_1 or based on a configured grant, the TRP index can be derived from the TRP index configured for associated SRS indicated by DCI or configured by higher layer signaling. In some implementations, for PUSCH which is dynamically scheduled by DCI format 0_0, the TRP index can be derived from the PUCCH resource with lowest resource ID in active bandwidth part. In some implementations, for semi-persistent CSI report on PUCCH or PUSCH, TRP index can be configured within semiPersistentOnPUCCH or semiPersistentOnPUSCH. In some implementations, uplink channel associated with the same TRP index may indicate the uplink channel transmitted based on the same Radio Network Temporary ID (RNTI), or from the same antenna port(s) or antenna port(s) group or panel, or share the same subset of or all parameters in a PUSCH-Config or PUCCH-Config, or be configured in a PUSCH-Config or PUCCH-Config.

These and other techniques can be performed by an apparatus that is implemented in or employed by one or more types of network components, user devices, or both. In some implementations, one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more of the described techniques. An apparatus can include one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more of the described techniques.

The methods described here can be implemented in software, hardware, or a combination thereof, in different implementations. In addition, the order of the blocks of the methods can be changed, and various elements can be added, reordered, combined, omitted, modified, and the like. Various modifications and changes can be made as would be obvious to a person skilled in the art having the benefit of this disclosure. The various implementations described here are meant to be illustrative and not limiting. Many variations, modifications, additions, and improvements are possible. Accordingly, plural instances can be provided for components described here as a single instance. Boundaries between various components, operations and data stores are somewhat arbitrary, and particular operations are illustrated in the context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within the scope of claims that follow. Finally, structures and functionality presented as discrete components in the example configurations can be implemented as a combined structure or component.

The methods described herein can be implemented in circuitry such as one or more of: integrated circuit, logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), or some combination thereof. In some implementations, the circuitry may execute one or more software or firmware programs to provide at least sonic of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code can be referred to as a particular type of circuitry. Circuitry can also include radio circuitry such as a transmitter, receiver, or a transceiver.

A number of implementations have been described. Nevertheless, it will be understood that various modifications can be made. Elements of one or more implementations can be combined, deleted, modified, or supplemented to form further implementations. As yet another example, the logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desirable results. In addition, other steps can be provided, or steps can be eliminated, from the described flows, and other components can be added to, or removed from, the described systems. Accordingly, other implementations are within the scope of the following claims. 

What is claimed is:
 1. A method comprising: receiving, by a user equipment (UE) from one or more Transmission and Reception Points (TRPs), a physical downlink shared channel (PDSCH) transmission; determining, by the UE for a physical uplink control channel (PUCCH) carrying hybrid automatic repeat request acknowledgement (HARQ-ACK), a TRP index in accordance with a control resource set (CORESET) scheduling the PDSCH transmission; and transmitting, by the UE via the PUCCH, HARQ-ACK information based on the receiving of the PDSCH transmission in accordance with the TRP index.
 2. The method of claim 1, wherein the TRP index comprises a first index value, wherein the CORESET comprises a first CORESET and a second CORESET, wherein the first CORESET is associated with the first index value, wherein the second CORESET is associated with a second index value, wherein determining the TRP index comprises determining the first index value associated with the first CORESET and determining a second index value associated with the second CORESET, and wherein transmitting the HARQ-ACK information is responsive to the first index value and the second index value.
 3. The method of claim 2, wherein transmitting the HARQ-ACK information comprises: transmitting first HARQ-ACK information associated with the first CORESET; and transmitting second HARQ-ACK information associated with the second CORESET.
 4. The method of claim 2, wherein determining the first index value comprises using a default value for the first index value based on the first index value not being provided by a network.
 5. The method of claim 2, wherein determining the first index comprises using a CORESET index parameter configured by a radio resource control (RRC) layer.
 6. The method of claim 2., wherein transmitting the HARQ-ACK information comprises using the first index value and the second index value for HARQ-ACK codebook construction.
 7. The method of claim 1, wherein the TRP index is indicated by a ConfiguredGrantConfig information element provided by a radio resource control (RRC) layer.
 8. The method of claim 1, comprising: transmitting, on a physical uplink control channel (PUCCH), semi-persistent channel state information based on a TRP index configured by a radio resource control (RRC) layer.
 9. The method of claim 1, comprising: transmitting, on a physical uplink shared channel (PUSCH), semi-persistent channel state information based on a TRP index configured by a radio resource control (RRC) layer.
 10. The method of claim 1, wherein receiving the PUSCH transmission comprises receiving transmissions from multiple TRPs.
 11. A user equipment (UE) comprising: one or more processors; circuitry to wirelessly communicate with a network; and a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving, via the circuitry from one or more Transmission and Reception Points (TRPs) associated with the network, a physical downlink shared channel (PDSCH) transmission; determining, for a physical uplink control channel (PUCCH) carrying hybrid automatic repeat request-acknowledgement (HARQ-ACK), a TRIP index in accordance with a control resource set (CORESET) scheduling the PDSCH transmission; and transmitting, via the circuitry, HARQ-ACK information on the PUCCH based on the receiving of the PDSCH transmission in accordance with the TRP index.
 12. The UE of claim 11, wherein the TRP index comprises a first index value, wherein the CORESET comprises a first CORESET and a second CORESET, wherein the first CORESET is associated with the first index value, wherein the second CORESET is associated with a second index value, wherein determining the TRP index comprises determining the first index value associated with the first CORESET and determining a second index value associated with the second CORESET, and wherein transmitting the HARQ-ACK information is responsive to the first index value and the second index value.
 13. The UE of claim 12, wherein transmitting the HARQ-ACK information comprises: transmitting first HARQ-ACK information associated with the first CORESET; and transmitting second HARQ-ACK information associated with the second CORESET.
 14. The UE of claim 12, wherein determining the first index value comprises using a default value for the first index value based on the first index value not being provided by a network.
 15. The UE of claim 12, wherein determining the first index comprises using a CORESET index parameter configured by a radio resource control (RRC) layer.
 16. The UE of claim 12, wherein transmitting the HARQ-ACK information comprises using the first index value and the second index value for HARQ-ACK codebook construction.
 17. The UE of claim 11, wherein the TRP index is indicated by a ConfiguredGrantConfig information element provided by a radio resource control (RRC) layer.
 18. The UE of claim 11, wherein the operations comprise: transmitting, on a physical uplink control channel (PUCCH), semi-persistent channel state information based on a TRP index configured by a radio resource control (RRC) layer.
 19. The UE of claim 11, wherein the operations comprise: transmitting, on a physical uplink shared channel (PUSCH), semi-persistent channel state information based on a TRP index configured by a radio resource control (RRC) layer.
 20. The UE of claim 11, wherein receiving the PDSCH transmission comprises receiving transmissions from multiple TRPs. 